Install MobileFirst Server in WAS ND
To install IBM MobileFirst Platform Server in a set of WAS ND servers, run IBM Installation Manager on the machine where the deployment manager is running.
- When IBM Installation Manager prompts you to specify the database type, select any option other than Apache Derby. IBM MobileFirst Platform Foundation supports Apache Derby only in embedded mode, and this choice is incompatible with deployment through WAS ND.
- In the installer panel in which we specify the WAS installation directory, select the deployment manager profile.
Attention: Do not select an application server profile and then a single managed server: doing so causes the deployment manager to overwrite the configuration of the server regardless of whether you install on the machine on which the deployment manager is running or on a different machine.
- Select the required scope depending on where you want MobileFirst Server to be installed. The following table lists the available scopes:
Scope Explanation Cell Installs MobileFirst Server in all application servers of the cell. Cluster Installs MobileFirst Server in all application servers of the specified cluster. Node (excluding clusters) Installs MobileFirst Server in all application servers of the specified node not in a cluster. Server Installs MobileFirst Server in the specified server, which is not in a cluster.
- Restart the target servers by following the procedure in Complete the installation.
Results
The installation has no effect outside the set of servers in the specified scope. The JDBC providers and JDBC data sources are defined with the specified scope. The entities that have a cell-wide scope (the applications and, for DB2 , the authentication alias) have a suffix in their name that makes them unique. So, we can install MobileFirst Server in different configurations or even different versions of MobileFirst Server, in different clusters of the same cell.Because the JDBC driver is installed only in the specified set of application servers, the Test connection button for the JDBC data sources in the WebSphere Application Server administration console of the deployment manager might not work.
What to do next
You need to complete the following additional configuration:
- If we use a front-end HTTP server, we need to configure the public URL
Parent topic: Install Application Center with IBM Installation Manager