Configure WebSphere Application Server manually

To configure WebSphere Application Server manually, configure variables, custom properties, and class loader policies.

Find the SOAP port of the deployment manager (WAS ND only)

These instructions assume that a stand-alone profile exists with an application server named "Worklight" and that the server is using the default ports.

For WAS ND, find the SOAP port of the deployment manager:

1. Open the System Administration/dmgr.

2. In Additional properties, open Ports.

3. Note the value of SOAP_CONNECTOR_ADDRESS. Needed to set the value of the ibm.worklight.admin.jmx.dmgr.port environment entry for the administrative services.

Review the environment IDs

Specify an environment ID is optional. However, if we specify an ID, use the same value for each MobileFirst runtime environment managed by the same MobileFirst Server administration component. Moreover, this value must match the environment ID used when the MobileFirst Server administration component is installed. For more information about the ibm.worklight.admin.environmentid JNDI property, see Configure a MobileFirst project in production using JNDI environment entries.

1. Log on to theWebSphere Application Server administration console for the MobileFirst Server.

   The address is of the form http://server.com:9060/ibm/console, where server is the name of the server.

2. Create the MF_HOME variable:

   1. Click Environment > WebSphere Variables.

   2. From the Scope list, select Worklight server.

   3. Click New. The Configuration pane is displayed.

   4. In the Name field, type MF_HOME.

   5. In the Value field, type /opt/IBM/Worklight.

   6. Optional: In the Description field, type a description of the variable.

   7. Click OK.

   8. Save the changes.

3. Create the MobileFirst shared library definition:

   1. Click Environment > Shared libraries.

   2. From the Scope list, select Worklight server.

   3. Click New. The Configuration pane is displayed.

   4. In the Name field, type WL_PLATFORM_LIB.

   5. Optional: In the Description field, type a description of the library.

   6. In the Classpath field, type ${MF_HOME}/WorklightServer/worklight-jee-library.jar.

4. Create the MobileFirst JDBC data source and provider.

   See the instructions for the appropriate DBMS in Create the databases manually.

5. Add a specific web container custom property.

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

   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.

6. Install a MobileFirst project WAR file.

   In the following procedure, when the example uses worklight.war, use the name of the project. for example, myProject.war.

   1. Depending on the version of WebSphere Application Server, click one of the following options:

      • Applications > New > New Enterprise Application

      • Applications > New Application > New Enterprise Application

   2. Navigate to the MobileFirst Server installation directory MF_HOME/WorklightServer.

   3. Select worklight.war, and then click Next.

   4. On the "How do to install the application?" page, select Detailed, and then click Next.

   5. On the Application Security Warnings page, click Continue.

   6. Click Continue repeatedly until you reach Step 4 of the wizard: Map Shared Libraries.

   7. Select Select for worklight_war and click Reference shared libraries.

   8. From the Available list, select WL_PLATFORM_LIB and click >.

   9. Click OK.

   10. Click Next until you reach the "Map context roots for web modules" page.

   11. In the Context Root field, type /worklight.

   12. Click Next.

   13. In Map environment Entries for Web Module, we can assign the JNDI variables according to the configuration.

       • Set the variable ibm.worklight.topology.platform to WAS

       • Set the variable ibm.worklight.admin.jmx.connector to SOAP

       • If the environment ID is set for the administration services, set the variable ibm.worklight.admin.environmentid to the same value.

       • On a stand-alone WebSphere Application Server, set the value of ibm.worklight.topology.clustermode to Standalone

       • On WAS ND, set the variables as follows:

         • ibm.worklight.topology.clustermode: Cluster

         • ibm.worklight.admin.jmx.dmgr.host: the host name of the deployment manager

         • ibm.worklight.admin.jmx.dmgr.port: the SOAP port of the deployment manager

   14. Click Finish.

7. Optional: As an alternative to step 6, we can map the shared libraries as follows:

   1. Click Applications > Application Types > WebSphere enterprise applications > worklight_war.

   2. In the References section, click Shared library references.

   3. Select Select for worklight_war and click Reference shared libraries.

   4. From the Available list, select WL_PLATFORM_LIB and click >.

   5. Click OK twice to return to the worklight_war configuration page.

   6. Click the Save link.

8. Define the startup behavior.

   1. Click Applications > Application Types > WebSphere enterprise applications > worklight_war.

   2. Click Startup behavior.

   3. In Startup Order, enter 2.

      The MobileFirst Administration service must already be available when the MobileFirst runtime starts.

9. Configure the class loader policies and then start the application:

   1. Click the Manage Applications link, or click Applications > WebSphere Enterprise Applications.

   2. From the list of applications, click worklight_war.

   3. In the "Detail Properties" section, click the Class loading and update detection link.

   4. In the "Class loader order" pane, click Classes loaded with local class loader first (parent last).

   5. Click OK.

   6. In the Modules section, click Manage Modules.

   7. From the list of modules, click the MobileFirst module.

   8. In the "Class loader order" pane, click Classes loaded with local class loader first (parent last).

   9. Click OK twice.

   10. Click Save.

   11. Select Select for worklight_war and click Start.

10. Review the server class loader policy: Click Servers > Server Types > Application Servers > Worklight

    • If the class loader policy is set to Multiple, do nothing.

    • If the class loader policy is set to Single and the class loading mode is set to parent-last, do nothing.

    • If the class loader policy is set to Single and the class loading mode is set to parent-first, change the class loader policy to Multiple, and set the class loader order of all applications other than MobileFirst applications to parent-first.

Results

We can now view the runtime component from the MobileFirst Administration Console installed in Install administration services and the operations console. The default URL of the MobileFirst Administration Console is http://server:port/worklightconsole, where server is the host name of the server and port is the port number (default value 9080).

Parent topic: Deploy a project WAR file manually.