This guide goes through the steps of installing the Apprenda Cloud Platform using the Apprenda Platform Installer user interface. It assumes you are setting up a multi-node environment, but the same steps can be used if you are only installing on a single node.
The Platform Installer will only install Apprenda on Windows nodes. If you plan to include Linux nodes in your Platform, you can add them to your Platform after you install the Platform on at least one Windows node. See more about installing Linux nodes.
Before installing, make sure your environment is properly configured by following these guides:
To install you must have
Start by opening the Apprenda.Wizard.exe from the Installer folder of the Apprenda Cloud Platform package. In the first screen select Install and click Next.
On the Welcome to Apprenda screen,
Then, click Next.
The following page displays Terms & Conditions for using the Apprenda Cloud Platform.
Then, click Next.
On the How would you like to license Apprenda? screen,
Once you have selected a license file, the screen will show you the licensed attributes you will be able to use on the Platform. For Hybrid Cloud installations, your license file should encompass the URLs for all Clouds being installed. If you have an questions about your license, contact your support representative.
The next screen, Tell us who you are, is used to configure the initial Development Team account as well as the initial Platform Operator. You can use these accounts to log into the Platform after installation and begin configuring your Platform.
Fill in your company information and user credentials for all required fields. Company Alias, Administrator Email, and Administrator Password are used to create a special tenant on the Platform. If you are using Identity Federation and an External User Store, it is important that the Company Alias and Administrator Email not conflict with any tenant alias or user ID which will be returned by the EUS. If a conflict occurs, that user will not be able to log into the Platform.
On the Apprenda Needs to Send Emails. What Should it Use? screen, you can select how you’d like the Platform to send emails. The Platform will use the configured email service to help you monitor your Platform by send log or error messages from your guest applications.
Using the Platform service to send emails is selected by default, but its recommended that you provide your own SMTP server for production environments. To use your own SMTP server,
Click Next when you are finished configuring.
On What Windows Users Should Apprenda Run As?, you should fill in the account information for the Administrator Account and Apprenda System Account used by the Platform to launch and manage websites and servers. These accounts require specific configuration settings to install correctly, see the Pre-Installation Checklist and the Platform accounts page for more information about the correct setup for these accounts.
The Platform uses Virtual Accounts by default to manage Windows Services to increase security and simplify managing users. See more information about Virtual Accounts.
Fill in the domain, user name, and password. Click Next when you finish.
For the Configure Clouds screen input information for the Clouds of your Platform. The Platform supports multiple Clouds and this screen is where you can input basic information about each Cloud.
After filling in this information for a single Cloud, if you have another Cloud to add to your Platform, select Add Another Cloud. The same information should be provided for any additional clouds you want to add. For each Cloud you configure, you will need to fill out the subsequent Installer screens for configuring the nodes in each Cloud:What Servers Should We Start Off With?, What Database Servers Should We Start Off With?, Where Should We Install The Coordination Cluster Nodes?, Where Should We Install the Load Manager Server?, Where Should We Install the Cache Service?.
To switch between Clouds on this screen, click on the cloud icon with the name of the Cloud you want to view.
When you finish adding Clouds, click Next.
The What Servers Should We Start Off With? screen asks for information about the nodes in a given Cloud. If you configured multiple Clouds on the previous screen, you should only add servers for the current Cloud. You will be able to configure nodes for other Clouds in the Platform later. The Cloud Name of the current cloud is shown above the boxes to input servers. Note that only Windows servers should be added on this screen and you can add Linux Servers after the Platform is installed.
To add a server
The servers will appear in the corresponding box for Web Servers or Application Servers. Note that a server can be both a Web Server and an Application Server. See more about server roles.
To remove a server
Once you have finished configuring the servers for this Cloud, click Next.
On the What Database Servers Should We Start Off With? the Installer asks for information about the database nodes of the Platform. If you configured multiple Clouds, you should only add database servers for the current Cloud. The Cloud Name of the current cloud is shown above the boxes to input databases.
To add a database
To remove a database
Note that if you want to edit a database server that has already been added, you will need to remove the database and re-add it with the correct information.
After configuring all database servers for a Cloud, click Next.
On Where Should We Install The Coordination Cluster Nodes? you can select nodes that should be used for Platform coordination for the current Cloud. If you configured multiple Clouds, you should select servers for the current Cloud only. The Cloud Name of the current cloud is shown above the list of nodes. See more about Platform roles.
It’s recommended that you assign an odd number of servers for this role as a majority of Platform Coordination nodes ((n+1)/2, where n=the number of nodes) must be up and running in order for the Platform to function properly.
Nodes added as Web Servers and Application Servers for the Cloud on the What Servers Should We Start With? screen will appear here as available options for the Platform Coordinator role. You may also choose to use off Platform servers for your coordination cluster. Note that you can’t use a combination of on Platform and off Platform servers to make up you coordination cluster.
To add servers that will not be part of the Platform for your coordination cluster
You can remove an added server by clicking on a server and clicking Remove Selected Host.
To assign a server as the Platform Coordinator role
Click Next when you finish.
In the following screen, Where Should We Install the Load Manager Server?, you can assign which node will act as a Load Manager for this Cloud. If you configured multiple Clouds, you should select servers for the current Cloud only. The Cloud Name of the current cloud is shown above the list of nodes. See more about Platform roles.
You may use nodes that are not a part of the Platform for this role. Note that if your Platform installation will include more than one Load Manager, Load Manager nodes can’t also be selected as Web Servers (assigned on What Servers Should We Start Off With?).
To add servers that will not be part of the Platform for load management
You can remove an added server by clicking on a server and clicking “Remove Selected Host.”
To assign a server this the Platform Coordinator role
Once you have selected the node, click the Next button:
The Where Should We Install the Cache Service? screen covers Cache Service target selection. If you configured multiple Clouds, you should select servers for the current Cloud only. The Cloud Name of the current cloud is shown above the list of nodes. See more about Platform roles. You may use nodes that are not a part of the Platform for this role.
To configure how the cache server will work on your Platform,
To add servers that will not be part of the Platform for the cache service,
You can remove an added server by clicking on a server and clicking Remove Selected Host.
To assign a server this the cache service role,
When you’re done, click Next. This is a last Cloud specific screen. If you have multiple Clouds to configure, clicking Next will bring you to the What Servers Should We Start Off With? screen where you can start configuring servers and roles for that Cloud. If you have only one Cloud, or have finished configuring all the clouds in your Platform, clicking next will bring you to the Choose the core database server screen.
On the next screen, Choose the core database server, you choose the Core Database for the entire Platform. The screen will display a list of all the SQL databases configured for the Platform. Note that the Core Database can’t be located on an Oracle database instance.
Select the database you’d like to act as a Core Database.
Click the Next.
The following screen, Configure Platform Auditing, is where you can optionally decide to enable Platform Auditing. Auditing will enable your Platform to log specific operations performed by users, such as password changes, login failures, updates to roles and securables, etc. You can only enable or disable this feature through the installer. Once it is turned on (or off) you must re-install the Platform to turn it off (or on).
To enable auditing
The Platform does not encrypt the Auditing database by default and it is your responsibility to enable any encryption configurations, like Transparent Data Encryption, on the supplied database.
When you’re done, click Next.
On the Linux Server Configuration screen you can provide your Platform with information about your Linux nodes. The Apprenda Installer only installs the Platform on Windows nodes and you must manually install Linux node onto an existing Platform. Information provided on this screen relates to how the Platform will be installed on Linux servers later.
When you’re done, click Next:
On the Installation Preferences screen, you can provide the Installer with information about how you’d like to install your Platform.
After you are done with your configuration, click the Next button:
The following screen, How Should Apprenda Manage Security?, will be used to configure the security of the Platform. Select all settings that you wish to apply to your Platform.
Click the Next button once you are done.
The next screen, Should Apprenda Encrypt Internal Communications?, offers you the option of enforcing encryption of internal Platform communications. To enable encryption, check the Encrypt internal communications box.
You will not be able to enable/disable internal Platform encryption in future. The setting for internal Platform encryption chosen when installing will be used throughout the lifetime of the Platform.
If you choose to enable internal encryption, you have three options in regards to the certificates that will be used:
Once you configure these options, click Next. You are now finished configuring your Platform. The remaining screens will validate your configurations and install your Platform!
The Configure My System & Network screen will validate your configuration settings and do some additional configuration steps to make sure that you are ready to install.
To start validation, click on the Validate My Configuration. Many incorrectly-configured items are automatically corrected by the Installer with no further input from you. If any configuration check fails, however, a red dot is displayed along with information about the failure and suggested actions for correction.
When all of them complete successfully, you will get a success message and will be able to click on the Next button to access the Install screen.
From the Install Apprenda screen you can begin installing your Platform!
Click Install to begin. If a task fails a red dot will be displayed next to it. Consider retrying in the event of a failure; otherwise, double-click on the event to get a detailed message of what caused the task to fail.
After all tasks are complete, you will have finished installing the Apprenda Cloud Platform. The Wizard will allow you to download the SDK if desired; otherwise, simply exit the Installer. Your Platform is now ready to be used.