IMS Mobile Feature Pack for z/OS Connect is no longer enhanced. Instead, use the IMS service provider that is included in IBM z/OS Connect Enterprise Edition V2.0.5 (APAR PI70432) or later, which not only supports later releases of the Liberty server but additionally provides support for REST API creation and deployment. For the latest IMS mobile solution information, see Using the IMS service provider in z/OS Connect EE documentation.

Roadmap for installing IMS Mobile Feature Pack as a feature in WebSphere Application Server for z/OS Liberty Profile

Use this roadmap to install IMS™ Mobile Feature Pack as a feature if you already have WebSphere Application Server for z/OS Liberty Profile.

Before you begin

Ensure that you meet the System and operational requirements.
Review Operational considerations and restrictions.
The WebSphere Liberty z/OS Connect feature must be installed.

About this task

Use the following installation roadmap to guide your installation and configuration.

Table 1. Roadmap for installing and configuring the IMS Mobile Feature Pack as a feature in WebSphere Liberty profile
Step	Description of task
1	If you can run the WebSphere Application Server for z/OS Liberty Profile installUtility -install command to install directly from an IBM-hosted repository, take the following steps. Go to https://developer.ibm.com/wasdev/downloads/. Enter "IMS Mobile Feature Pack" in the Search Liberty Repository assets search box. Follow the installation and configuration instructions are provided on the page. If you cannot run the installUtility -install command to install from an IBM-hosted repository, take the following steps. Go to IMS Enterprise Suite download site. Log in with your IBM® ID and password. Choose IMS Enterprise Suite - Version 3.2 and follow the instructions on the page to download the .esa file for IMS Mobile Feature Pack. Transfer the downloaded .esa file to a file system that the installUtility command can install from. From the `zosconnect_wlp_dir` directory, issue the following command: `./bin/installUtility install path_to_esa_file --to=imsmobile` `path_to_ESA_file` is the fully qualified path to where the .esa file is, including the file name. For example: `./bin/installUtility install /usr/lpp/myrepo/ims_mobile_esa_file_name.esa --to=imsmobile`
2	Configure IMS Mobile Feature Pack for z/OS Connect to specify the registry home, Java home, the technical group, and the technical ID.
3	For initial installation and quick installation verification in an environment without SAF configuration, you could use basic authentication. For more information, see Basic authentication configuration for IMS Mobile Feature Pack. For SAF configuration (required for production environments), see SAF configuration for IMS Mobile Feature Pack
4	Start the server by issuing: `START BBGZSRV` For more information, see the Administering the Liberty profile on z/OS topic in WebSphere Application Server for z/OS documentation.
5	Verify the installation by invoking the IMSPingService service.
6	Configure IMS Connect.
7	Verify server communication with IMS.