Configure WAS ND servers

Specific considerations when we configure WAS ND servers through Ant tasks are documented in this section.

To install a MobileFirst project into a set of WAS ND servers, run the <configureapplicationserver> Ant task on the computer where the deployment manager is running.

1. Specify a database type 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.

2. As value of the profile attribute, specify the deployment manager profile.

   Attention: Do not specify an application server profile and then a single managed server. Doing so causes the deployment manager to overwrite the configuration of the server. This is true whether you install on the computer on which the deployment manager is running or on a different computer.

3. Specify an inner element, depending on where you want the MobileFirst Runtime Component to be installed. The following table lists the available elements:

   We must choose the same inner element to install the administrative services. Install an instance of the MobileFirst administration service on each server where the MobileFirst Runtime Component is installed.

   Element	Explanation
   cell	Install the project.into all application servers of the cell.
   cluster	Install the project.into all application servers of the specified cluster.
   node	Install the project.into all application servers of the specified node not in a cluster.
   server	Install the project.into the specified server, which is not in a cluster.

4. After starting the <configureapplicationserver> Ant task, restart the affected servers:

   • We must restart the servers that were running and on which the project.application was installed. To restart these servers with the deployment manager console, select Applications > Application Types > WebSphere enterprise applications > IBM_Worklight_Console > Target specific application status.

   • We do not have to restart the deployment manager or the node agents.

Results

The configuration has no effect outside the set of servers in the specified scope. The JDBC providers, JDBC data sources, and shared libraries are defined with the specified scope. The entities that have a cell-wide scope (the applications and, for DB2 , the authentication alias) use the specified id attribute as a suffix in their name; it makes their name 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 administrative console of the deployment manager might not work.

Add a server to a cluster

When we add a server to a cluster that has a MobileFirst project installed on it, we must repeat some configuration manually. For each affected server, add a specific web container custom property:

1. Click Servers > Server Types > Application Servers, and select the server.

2. Click Web Container Settings > Web container.

3. Click Custom properties.

4. Click New.

5. Enter the property values listed in the following table:

   Property	Value
   Name	com.ibm.ws.webcontainer.invokeFlushAfterService
   Value	false
   Description	See http://www.ibm.com/support/docview.wss?uid=swg1PM50111.

6. Click OK.

7. Click Save.

Parent topic: Deploy a project WAR file and configure the application server with Ant tasks