Configure WebSphere Application Server for Application Center manually

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

These instructions assume that a stand-alone profile exists and that the application server is using the default ports.

1. Log on to the WebSphere Application Server administration console for the MPF Server.

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

2. Enable application security.

   1. Click Security > Global Security.

   2. Ensure that Enable administrative security is selected. Application security can be enabled only if administrative security is enabled.

   3. Ensure that Enable application security is selected.

   4. Click OK.

   5. Save the changes.
   See Enable security.

3. Create the Application Center JDBC data source and provider.

   See the instructions in the appropriate subsection in Manual installation of Application Center.

4. Install the Application Center console WAR file.

   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/ApplicationCenter/console.

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

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

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

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

   7. In the Context Root field, type /appcenterconsole.

   8. Click Next.

   9. Click Finish.

5. 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 appcenterconsole_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 ApplicationCenterConsole.

   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. Click Select for appcenterconsole_war and click Start.

6. Repeat step 4, selecting applicationcenter.war in substep c, and using a Context Root of /applicationcenter in substep g.

7. Repeat step 5, selecting applicationcenter.war from the list of applications in substep b.

8. Review the server class loader policy: Click Servers > Server Types > Application Servers and then select the server.

   • 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.

9. Configure a JNDI environment entry to indicate the directory with binary files of the aapt program, from the Android SDK platform-tools package.

   For a stand-alone server...

   1. Click Applications > WebSphere enterprise applications.

   2. From the list of applications, select applicationcenter_war.

   3. In the Web Module Properties section, select Environment entries for Web modules.

   4. To the variable android.aapt.dir assign the value MF_HOME/ApplicationCenter/tools/android-sdk, where MF_HOME is the MobileFirst Server installation directory.
   For WAS ND...

   1. Copy the MF_HOME/ApplicationCenter/tools/android-sdk directory to a location in the config directory of the deployment manager profile. This path is propagated to the servers through the file synchronization service;

      For example: wasnd_install_dir/profiles/Dmgr01/config/cells/mycell/clusters/cluster-name/android-sdk.

   2. Configure the environment entry android.aapt.dir with value ${USER_INSTALL_ROOT}/config/cells/mycell/clusters/cluster-name/android-sdk.

      The USER_INSTALL_ROOT placeholder represents the WebSphere variable that refers to the absolute path of the directory for WAS profiles.

   3. Click System administration > Nodes, select the nodes, and click Full Synchronize.

Results

We can now access the Application Center at http://server:port/appcenterconsole, where server is the host name of the server and port is the port number (by default 9080).

What to do next

For more steps to configure the Application Center, see Configure WAS full profile.

Parent topic: Deploy Application Center WAR files manually