+

Search Tips | Advanced Search

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


Deploy MobileFirst Application Center on a single-node WebSphere Application Server full profile server

We use a predefined template to deploy a single-node MobileFirst Application Center to a WebSphere® Application Server full profile server.


Before you begin

This procedure involves uploading certain artifacts to IBM® PureApplication® System such as the required application and adapter. Before you begin, ensure that the artifacts are available for upload.

Token licensing requirements: If we use token licensing to license IBM MobileFirst™ Platform Foundation, review the requirements outlined in Token licensing requirements for IBM MobileFirst Platform Foundation System Pattern before you continue. The deployment of this pattern fails if the license key server cannot be contacted or if insufficient license tokens are available.

Note:

Some parameters of script packages in the template have been configured with the recommended values and are not mentioned in this section. For fine-tuning purposes, see more information about all the parameters of script packages in Script packages for MobileFirst Server.

For more information about the composition and configuration options of the predefined template that is used in this procedure, see MobileFirst Platform Application Center (WAS single node) template.


Procedure

  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 (AppCenter Liberty single node) from the list of predefined templates. If the name is only partially visible due to its length, we 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 MFP AppCenter 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 MFP AppCenter 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 MFP AppCenter DB node, select the Default add disk component, and then click the bin icon to delete it.
    6. Save the pattern.
  3. Optional: Configure MFP Server Application Center in the MFP AppCenter Server node.

    Note: If we want to configure administration security with an LDAP server, you need to supply additional LDAP information. For more information, see Configure MobileFirst administration security with an external LDAP repository.

    1. In the MFP AppCenter Server node, click the MFP Server Application Center 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. Next to the db_user and db_password fields, click the Delete button to clear their pattern level parameter settings.
    5. In the db_user and db_password fields, specify the database user name and password.
    6. In the db_name, db_instance, db_ip, and db_port fields, specify the database user name, password, instance name, IP, and port number.
    A default administration account for MobileFirst Server is created during pattern deployment.
  4. 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 Configure MobileFirst administration security with an external LDAP repository.

        admin_user
        Not visible if configured in step 3. Create a default MobileFirst Server administrator account. Default value: demo.
        admin_password
        Not visible if configured in step 3. Default admin account 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 we use perpetual licenses.
        LICENSE_SERVER_HOSTNAME
        Not visible if configured in step 3. If we 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 we 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 we 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 "/".
        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, we 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.

    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. We 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 our pattern there.
  5. To access the MobileFirst Operations Console perform the following steps:

    1. Click Patterns > Virtual System Instances to open the Virtual System Instances page and search for our pattern there.
    2. Select your pattern name and expand the Virtual machine perspective in the panel that displays the details of the selected instance.
    3. Find the MobileFirst Server VM that has a name similar to MFP_AppCenter_Server.*, make a note of its public IP address.
    4. In the browser, open the MobileFirst Operations Console by composing its URL with one of the following formats:

      • http://{MFP Server VM Public IP}:9080/appcenterconsole
      • https://{MFP Server VM Public IP}:9443/appcenterconsole

    5. Log in to the Console with admin user and password specified in step 3.

Parent topic: Deploy MobileFirst Server on IBM PureApplication System