For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.


Configure WebSphere Application Server for Application Center manually

After you deploy the Application Center EAR file, to configure WebSphere® Application Server profile manually for Application Center, we must configure variables, custom properties, and class loader policies.


Before you begin

Make sure that a WebSphere Application Server profile exists.


Procedure

  1. Log on to the WebSphere Application Server administration console for our IBM MobileFirstâ„¢ Platform 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.
    For more information, see Enabling security.
  3. Create the Application Center JDBC data source and provider.

    See the appropriate section in Manually installing Application Center.

  4. Install the Application Center EAR file.
    1. Depending on your version of WebSphere Application Server, click one of the following options:

      • Applications > New > New Enterprise Application
      • Applications > New Application > New Enterprise Application
    2. Go to the MobileFirst Server installation directory mfserver_install_dir/ApplicationCenter/console.
    3. Select applicationcenter.ear, and then click Next.
    4. On the How do we want to install the application? page, click Detailed, and then click Next.
    5. Click Next until you reach the "Map resource references to resources" page.
    6. Click Browse and select the data source with the jdbc/AppCenterDS JNDI name.
    7. Click Next until you reach the "Map context roots for web modules" page.
    8. In the Context Root fields, if they are not already set, type /appcenterconsole for the ApplicationCenterConsole module and type /applicationcenter for the ApplicationCenterServices module.
    9. Click Next until you reach the "Map security roles to users or groups" page.
    10. Select all roles, click Map Special Subjects and select All Authenticated in Application's Realm.
    11. Click Next until you reach the Summary page.
    12. Click Finish and save the configuration.
  5. Configure the class loader policies and then start the application:
    1. Click Applications > Application types > WebSphere Enterprise Applications.
    2. From the list of applications, click AppCenterEAR.
    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.
    10. From the list of modules, click ApplicationCenterServices.
    11. In the Class loader order pane, click Classes loaded with local class loader first (parent last).
    12. Click OK twice.
    13. Click Save.
    14. Select AppCenterEAR and click Start.
  6. Review the server class loader policy:

    Depending on your version of WebSphere Application Server, click Servers > Server Types > Application Servers or Servers > Server Types > WebSphere 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 Class loading mode is set to Classes loaded with local class loader first (parent last), do nothing.
    • If Classloader policy is set to Single and Class loading mode is set to Classes loaded with parent class loader first, set Classloader policy to Multiple and set the class loader policy of all applications other than MobileFirst applications to Classes loaded with parent class loader first.
  7. Save the configuration.
  8. Configure a JNDI environment entry to indicate the directory with binary files of the aapt program, from the Android SDK platform-tools package.
    1. Determine a suitable directory for the aapt binary files in the WebSphere Application Server installation directory.

      • For a stand-alone server, we can use a directory such as WAS_INSTALL_DIR/optionalLibraries/IBM/mobilefirst/android-sdk.
      • For deployment to a WebSphere Application Server Network Deployment cell, use WAS_INSTALL_DIR/profiles/profile-name/config/cells/cell-name/mobilefirst/android-sdk.
      • For deployment to a WebSphere Application Server Network Deployment cluster, use WAS_INSTALL_DIR/profiles/profile-name/config/cells/cell-name/clusters/cluster-name/mobilefirst/android-sdk.
      • For deployment to a WebSphere Application Server Network Deployment node, use WAS_INSTALL_DIR/profiles/profile-name/config/cells/cell-name/nodes/node-name/mobilefirst/android-sdk.
      • For deployment to a WebSphere Application Server Network Deployment server, use WAS_INSTALL_DIR/profiles/profile-name/config/cells/cell-name/nodes/node-name/servers/server-name/mobilefirst/android-sdk.
    2. Copy the product_install_dir/ApplicationCenter/tools/android-sdk directory to the directory that you determined in Substep a.
    3. For WebSphere Application Server Network Deployment, click System administration > Nodes, select the nodes, and click Full Synchronize.
    4. Configure the environment entry (JNDI property) android.aapt.dir and set as its value the directory that you determined in Substep a. The WAS_INSTALL_DIR/profiles/profile-name profile is replaced with the WebSphere Application Server variable reference ${USER_INSTALL_ROOT}.


Results

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


What to do next

For more steps to configure the Application Center, see Configuring the Java EE security roles on WebSphere Application Server full profile.

Parent topic: Deploying the Application Center EAR file and configuring the application server manually