Deploying MobileFirst Server on a multiple-node WebSphere Application Server full profile server

You use a predefined template to deploy MobileFirst Server on a multiple-node WebSphere® Application Server full profile server.

1. Create a pattern from the predefined template:
   1. In the IBM PureApplication System dashboard, click Patterns > Virtual System Patterns. The Virtual System Patterns page opens.
   2. On the Virtual System Patterns page, click Create New, and then in the pop-up window, select MobileFirst Platform (WAS server farm) from the list of predefined templates. If the name is only partially visible due to its length, you can confirm that the correct template is selected by viewing its description on the More information tab.
   3. In the Name field, provide a name for the pattern.
   4. In the Version field, specify the version number of the pattern.
   5. Click Start Building.
2. Mandatory for AIX®: In IBM PureApplication System running on Power®, the MobileFirst Platform DB node needs to use the AIX-specific add-on component "Default AIX add disk" to replace the "Default add disk" component in the template to support the jfs2 file system:
   1. In the Pattern Builder, select the MobileFirst Platform DB node.
   2. Click the Add a Component Add-on button (the button is visible above the component box when you hover the cursor over the MobileFirst Platform DB node).
   3. From the Add Add-ons list, select Default AIX add disk. The component is added as the lowest component of the MobileFirst Platform DB node.
   4. Select the Default AIX add disk component and specify the following attributes:

      DISK_SIZE_GB

      Storage size (measured in GB) to be extended to the DB server. Example value: 10.

      FILESYSTEM_TYPE

      Supported file system in AIX. Default value: jfs2.

      MOUNT_POINT

      Align with the attribute Mount point for instance owner in the Database Server component in the MobileFirst Platform DB node. Example value: /dbinst.

      VOLUME_GROUP

      Example value: group1. Contact your IBM PureApplication System administrator for the correct value.

   5. In the MobileFirst Platform DB node, select the Default add disk component, and then click the bin icon to delete it.
   6. Save the pattern.
3. Optional: Configure MobileFirst Server administration. You can skip this step if you want to specify the user credential with MobileFirst Server administration privilege later during the pattern deployment configuration phase in step 9. To specify it now, complete these steps:
   Note: If you want to configure administration security with an LDAP server, you need to supply additional LDAP information. For more information, see Configuring MobileFirst administration security with an external LDAP repository.
   1. In the MobileFirst Platform Server node, click the MFP Server Administration component. The properties of the selected component are displayed next to the canvas.
   2. Next to the admin_user and admin_password fields, click the Delete button to clear their pattern level parameter settings.
   3. In the admin_user and admin_password fields, specify the administration user name and password.
   4. If you use token licensing to license IBM MobileFirst Platform Foundation, complete the following fields. If you do not use token licensing, leave these fields blank.

      ACTIVATE_TOKEN_LICENSE

      Select this field to license your pattern with token licensing.

      LICENSE_SERVER_HOSTNAME

      Enter the fully qualified host name or IP address of your Rational License Key Server.

      LMGRD_PORT

      Enter the port number that the license manager daemon (lmrgd) listens for connections on. The default license manager daemon port is 27000.

      IBMRATL_PORT

      Enter the port number that the vendor daemon (ibmratl) listens for connections on. The default vendor daemon port is typically 27001.

   A default administration account for MobileFirst Server is created during pattern deployment.
4. Optional: Configure MobileFirst Server runtime deployment. You can skip this step if you want to specify the context root name for the runtime later during the pattern deployment configuration phase in step 10. To specify the context root name now, complete these steps:
   1. In the MobileFirst Platform Server node, click the MFP Server Runtime Deployment component. The properties of the selected component are displayed next to the canvas.
   2. Next to the runtime_contextRoot field, click the Delete button to clear the pattern level parameter setting.
   3. In the runtime_contextRoot field, specify the runtime context root name. Note that the context root name must start with a forward slash, /; for example, /HelloWorld.
5. Upload application and adapter artifacts:
   Important: When specifying the Target path for applications and adapters, make sure all the applications and adapters are placed in the same directory. For example, if one target path is /opt/tmp/deploy/HelloWorld-common.json, all the other target paths should be /opt/tmp/deploy/*.
   1. In the MobileFirst Platform Server node, click the MFP Server Application or MFP Server Adapter component. The properties of the selected component are displayed next to the canvas.
   2. In the Additional file field, click the Browse button to locate and upload the application or adapter artifact.
   3. In the Target path field, specify the full path for storing the artifact including its file name; for example, /opt/tmp/deploy/HelloWorld-common.json.
   4. If no application or adapter is to be deployed in the pattern, remove the relevant component by clicking the X button inside it. To get an empty MobileFirst Operations Console deployed without any app or adapter installed, remove the MFP Server Application Adapter Deployment component by clicking the X button inside it.
6. Optional: Add more application or adapter artifacts for deployment:
   1. From the Assets toolbar, expand Software Components, and then drag and drop an Additional file component onto the MobileFirst Paltform Server node in the canvas. Rename it MobileFirst App_X or MobileFirst Adatper_X (where X stands for a unique number for differentiation).
   2. Hover the cursor over the newly added App or Adapter component, and then click the Move Up and Move Down buttons to adjust its sequence in the node. Make sure it is placed after the MFP Runtime Deployment component but before the MFP Server Application Adapter Deployment component.
   3. Click the newly added App or Adapter component. The properties of the selected component are displayed next to the canvas. Upload the application or adapter artifact and specify its target path by referring to steps 6b-c.
   4. Repeat steps 7a-c to add more applications and adapters for deployment.
7. Optional: Configure MobileFirst Server application and adapter deployment. You can skip this step if you want to specify the user credential with deployment privilege later during the pattern deployment configuration phase in step 10. If you have specified the default admin user credential in step 3, you can now specify the deployer user, which should align with the admin user credential:
   1. In the MobileFirst Platform Server node, select the MFP Server Application Adapter Deployment component. The properties of the selected component are displayed next to the canvas.
   2. Find the parameters named deployer_user and deployer_password, and then click the Delete buttons to clear the Pattern Level Parameter settings.
   3. In the deployer_user and deployer_password fields, specify the user name and password.
8. Configure base scaling policy:
   1. In the MobileFirst Platform Server node, select the Base Scaling Policy component. The properties of the selected component are displayed next to the canvas.
   2. In the Number of Instances field, specify the number of server nodes to be instantiated during pattern deployment. The default value is 2 in the predefined template. Because dynamic scaling is not supported in this release, do not specify values in the remaining attribute fields.
9. Configure and launch the pattern deployment:
   1. In the IBM PureApplication System dashboard, click Patterns > Virtual System Patterns.
   2. On the Virtual System Patterns page, use the Search field to find the pattern you created, and then select the pattern.
   3. In the toolbar above the panel displaying detailed information about the pattern, click the Deploy button.
   4. In the Deploy Pattern window, in the Configure panel, select the correct environment profile from the Environment Profile list, and provide other IBM PureApplication System environment parameters. To obtain the correct information, consult your IBM PureApplication System administrator.
   5. In the middle column, click Pattern attributes to display attributes such as user names and passwords.

      Supply the following information in the fields provided:

      Note: Make appropriate changes to the default values of the pattern-level parameters even if an external LDAP server is configured. If you configure administration security by using an LDAP server, you need to supply additional LDAP information. For more information, see Configuring MobileFirst administration security with an external LDAP repository.

      runtime_contextRoot_list

      Context root names of the MobileFirst Server runtimes in case multiple runtimes exist. Use a semicolon, ";" to separate each runtime context root; for example, HelloMobileFirst;HelloWorld

      Important: runtime_contextRoot_list must align with the context root specified in the MFP Server Runtime Deployment node; otherwise, IHS will not be able to correctly route requests that contain the runtime context root.

      WebSphere administrative user name

      Admin user ID for WebSphere administration console login. Default value: virtuser.

      WebSphere administrative password

      Admin user password for WebSphere administration console login. Default value: passw0rd.

      admin_user

      Not visible if configured in step 3. Create a default user as MobileFirst Server administrator. Default value: demo.

      admin_password

      Not visible if configured in step 3. Default admin user password. Default value: demo.

      ACTIVATE_TOKEN_LICENSE

      Not visible if configured in step 3. Select this field to license your pattern with token licensing. Leave this field clear if you use perpetual licenses.

      LICENSE_SERVER_HOSTNAME

      Not visible if configured in step 3. If you use token licensing to license IBM MobileFirst Platform Foundation, enter the fully-qualified hostname or IP address of your Rational License Key Server IP address. Otherwise, leave this field blank.

      LMGRD_PORT

      Not visible if configured in step 3. If you use token licensing to license IBM MobileFirst Platform Foundation, enter the port number that the license manager daemon (lmrgd) listens for connections on. Otherwise, leave this field blank.

      The default license manager daemon port is 27000.

      IBMRATL_PORT

      Not visible if configured in step 3. If you use token licensing to license IBM MobileFirst Platform Foundation, enter the port number that the vendor daemon (ibmratl) listens for connections on. Otherwise, leave this field blank.

      The default vendor daemon port is typically 27001.

      runtime_contextRoot

      Not visible if configured in step 5. Context root name for the MobileFirst Server runtime. The name must start with a forward slash, /.

      deployer_user

      Not visible if configured in step 8. User name for the account with deployment privilege. If an external LDAP server is not configured, you must enter the same value as was specified when creating the default admin user for the administration service, because in this case, the only authorized user for app and adapter deployment is the default admin user.

      deployer_password

      Not visible if configured in step 8. User password for the user with deployment privilege.

      MFP Vms Password(root)

      Root password for the MobileFirst Platform Server and MobileFirst Platform DB nodes. Default value: passw0rd.

      MFP DB Password(Instance owner)

      Instance owner password for the MobileFirst Platform DB node. Default value: passw0rd.

      Important restriction:

      When you set these attrbutes, do not change the following attributes in the MobileFirst Platform Server section:

      • Cell name
      • Node name
      • Profile name

      If you change any of these attributes, your pattern deployment will fail.
   6. Click Quick Deploy to launch your pattern deployment. After a few seconds, a message is displayed to indicate that the pattern has started to launch. You can click the URL provided in the message to track your pattern deployment status or go to Patterns > Virtual System Instances to open the Virtual System Instances page and search for your pattern there.
   If you use token licensing to licenseIBM MobileFirst Platform Foundation, your pattern will fail to deploy if insufficient license tokens are available or if the license key server IP address and port were entered incorrectly.
10. Access the MobileFirst Operations Console:
    1. Click Patterns > Virtual System Instances to open the Virtual System Instances page and search for your pattern there. Make sure it is in Running state.
    2. Select the pattern name and expand the Virtual machine perspective option in the panel displaying details of the selected instance.
    3. Find the IHS Server VM that has a name similar to IHS_Server.* and make a note of its Public IP address: you need this information in the following step.
    4. In the browser, open the MobileFirst Operations Console by composing its URL with one of the following formats:
       • http://{IHS Server VM Public IP}/mfpconsole
       • https://{IHS Server VM Public IP}/mfpconsole
    5. Log in to the Console with admin user and password specified in step 3 or step 10.