Create a WebSphere Application Server Liberty server for the web services

Some RESTful web services, such as the web services for Participant Directory, use a WebSphere® Application Server Liberty server to run.

A compressed file that has WebSphere Application Server Liberty is installed when you install Financial Transaction Manager. Payment Feature Services provides the web services for its components in deployment files that you can use with WebSphere Application Server Liberty. The following table shows the deployment information that you need for the Payment Feature Services components.

Table 1. Deployment information for the WebSphere Application Server Liberty web services
Description	Server name	Deploy file name	Deploy file directory
Payment Feature Services web services	pfs	WebServices_PFS.war	`install_directory`/shared/v3213/pfs/WebServices/Liberty/pfs
Payment Feature Services transactions web services	PFSTransactions	WebServices_PFSTransactions.war	`install_directory`/shared/v3213/pfs/WebServices/Liberty/PFSTransactions
Business Rules Server web services	BusinessRules	WebServices_BusinessRulesEAR.ear	`install_directory`/shared/v3213/pfs/WebServices/Liberty/BusinessRules
Gateway Server web services	Gateway	WebServices_Gateway.war	`install_directory`/shared/v3213/pfs/WebServices/Liberty/Gateway
Web services or web services engine	webServices	WebServices_EAR.ear You also need to deploy all the user interface EAR files that are in the same location.	`install_directory`/shared/v3213/pfs/WebServices/Liberty/WebServices
Zelle web services	Zelle	Webservices_Zelle.war	`install_directory`/shared/v3213/pfs/WebServices/Liberty/Zelle

Use the following instructions to install WebSphere Application Server Liberty from FTM and then create and start a WebSphere Application Server Liberty server for the web services that you want to use.

Locate the compressed file for WebSphere Application Server Liberty in the ftm_install_directory/ftm/v3213/run/liberty directory.
Extract the file to the directory that you want to use for WebSphere Application Server Liberty. For example, /opt/wlp/. This directory is referred to as liberty_install_directory in the rest of these instructions.
Create and configure the server by using the following steps. The information that you need to use for the specific server you want to create is shown in Table 1.
1. Create the server by using the following command. Use the server name for the web services that you want to deploy as the server_name.
```
liberty_install_directory/bin/server create server_name
```
2. Update the following files with the configuration values that are specific to your installation.
  - deploy_file_directory/server.xml. For more information, see Server.xml file updates for the WebSphere Application Server Liberty server configuration.
  - deploy_file_directory/jvm.options. For more information, see JVM updates for the WebSphere Application Server Liberty server configuration.
  - deploy_file_directory/server.env. For more information, see Configuration updates for the Business Rules Server web services and Configuration updates for the Web Services web services.
  - Any other configuration file that you want to update in the deploy_file_directory. For more information, see Other property file updates for the WebSphere Application Server Liberty server configuration.
3. Copy the following updated configuration files to the liberty_install_directory/usr/servers/server_name directory.
  - deploy_file_directory/server.xml
  - deploy_file_directory/jvm.options
  - Any other configuration file that you updated in the deploy_file_directory.
4. Copy the deployment file for your server to WebSphere Application Server Liberty. For example,
  - Copy deploy_file_directory/deploy_file_name to liberty_install_directory/usr/servers/server_name/app.
5. Start your server by using the following command:
```
liberty_install_directory/bin/server start server_name
```
6. You might also need to install some more features for your server. Check the log files for any messages that indicate which features are missing and need to be installed. By default, the messages log file for the server is in the liberty_install_directory/usr/servers/server_name/logs directory.
7. Use the WebSphere Application Server Liberty installation utility to install the features that are missing. For example,
```
liberty_install_directory/bin/installUtility install feature_name
```
8. If you installed any features, stop and then start your server.

Server.xml file updates for the WebSphere Application Server Liberty server configuration

The configuration information in the following list might need to be modified in the server.xml file. The values to use depend on the details of your specific environment.

The client installation location for the Db2® drivers.
The database name and port number for the FTM database.
The user ID and password for the Db2 administrator. By default, this user ID is db2admin.
Set currentPackagePath, currentFunctionPath, and currentSchema to your schema name.
The client installation location for the IBM® MQ resource adapter driver.
The IBM MQ queue manager name, user ID, password, and port number.
The password for the administrator user ID that you use to access FTM. This user ID is usually fxhadmin.

Depending on your environment, more parameters might need to be changed.

JVM updates for the WebSphere Application Server Liberty server configuration

Depending on your environment, the startup options in the jvm.options file might need to be changed. For example, if you need to increase the default heap size, edit the file to add or change the following parameter.

-Xmx2048m

Other property file updates for the WebSphere Application Server Liberty server configuration

The web services for a Payment Feature Services component might have other property or configuration files that need to be updated. The following topics provide information for the components with other property files.