Verifying the WebSphere Application Server installation

To verify whether the WebSphere® Application Server is installed and configured successfully, perform the following steps:

If only one application server is to be used, start the application server. If more than one application server is to be used:
1. Start the WebSphere Deployment Manager.
2. Start the node agents on each server that belongs the cell.
3. Start the application servers on which you deployed the enterprise applications and check that all servers are successfully started.
Log on to the administrative console as the WebSphere Application Server administrator. The recommended user ID of this user is uwasa1. The access rights of this user are described in Table 1.
Check that the database connections are correctly configured:
1. Select Resources > JDBC > Data Sources.
2. If you created the JAAS J2C authentication aliases with a default password, update them with the actual passwords now. The JAAS J2C authentication aliases are described in JAAS J2C authentication aliases. To update the passwords, click the link for one of the data sources listed in Table 1, then select Related Items > JAAS - J2C authentication data to obtain a list of authentication aliases. The authentication alias names start with the same prefix as the data source names. After you update the passwords, restart the application server and return to the list of data sources.
3. In the list of data sources, for each of the following data source names, select the name and click on Test Connection:
  
  Table 1. Data sources
  
  Data source Default name Default JNDI name
  
  runtime DNIvINST_Runtime_DS jdbc/dni/db
  
  reference data DNIvINST_RefData_DS jdbc/dni/refdata
A message should be displayed on the console that indicates that the connection was successfully established.
If any of the connections were not successfully established, check whether:
- The Db2® user name and password for accessing the database (this information is in the JAAS authentication alias for the data source) are correct
- The database host name, port, and name are correctly specified
- The database is started
- There is a firewall between the application server and the database system
- The data source environment variables are set correctly
- The complete WebSphere Application Server environment was restarted since the last change was made to a security setting
- The JDBC provider classpath definition is correct. Check for example that the referenced JAR files exist and are accessible by the application server
Check that the enterprise applications are installed and correctly configured:
1. Click Applications > Application Types > WebSphere enterprise applications to obtain a list of installed enterprise applications. The FTM SWIFT enterprise applications use the following naming scheme:
```
DNIvINST_FTM_for_SWIFT_entapp
```
  where entapp represents an FTM SWIFT enterprise application:
  
  Home
  
  FTM SWIFT Home page, which lists all the other FTM SWIFT enterprise applications that are available from the a particular web server.
  
  MER
  
  Message Entry and Repair (MER) Facility.
  
  RMA
  
  Relationship Management Application (RMA).
  
  AO
  
  Administration and Operation (AO) Facility.
  
  The enterprise applications are described in Manually installing and uninstalling enterprise applications.
2. If you installed the enterprise applications manually, check that the environment entries are correctly set. For each enterprise application:
  1. Click the name of the enterprise application.
  2. Select Web Module Properties > Environment entries for web modules.
  3. Verify that the values are set according to Table 2.

Table 1. Data sources
Data source	Default name	Default JNDI name
runtime	DNIvINST_Runtime_DS	`jdbc/dni/db`
reference data	DNIvINST_RefData_DS	`jdbc/dni/refdata`

Check that the enterprise applications can be successfully initialized:

Ensure that you have access to the database and can communicate with the FTM SWIFT services running in the broker.
Set up and assign security roles for the Web-application queue accessor user (UWEBQA1). The access rights of this user are described in Table 1.
Choose a user:
- For the Message Entry and Repair (MER) Facility, choose a user who has the role DnqERMsgAdmin for any one OU.
- For the Relationship Management Application (RMA) or Administration and Operation (AO) Facility, choose a user who has the role DniSA in SYSOU.
Allow the chosen user to log in to the application server and to use the corresponding enterprise application.

In a browser, open the URL of each enterprise application that is to be tested:

If there is not an HTTP server in front of the server on which the enterprise application is installed (this is often done for test systems):
```
https://applhostname:port/context_root/
```
If there is an HTTP server in front of the server on which the enterprise application is installed (this is often done for production systems):
```
https://http_hostname/context_root/
```

where:

applhostname

The host name or IP address of the application server on which the enterprise application is installed.

httphostname

The host name or IP address of the HTTP server.

port

The port number at which the application server (or, if a web server is used, the web server) is to listen for the enterprise application. If port 443 is used, you can omit the port number and the leading colon (:).

contextroot

The context root that is used for the enterprise application:

Enterprise application	Context root
WebHome	/ftm-swift/
MER Facility	/dnqmer/
RMA	The value of the DNFvRMACONTROOT customization placeholder. The default is /rma/.
AO Facility	The value of the DNPvAOCONTROOT customization placeholder. The default is /ao/.

After you have authenticated on the WebSphere Application Server:
- For the MER Facility, the list of all OUs for which the role DnqERMsgAdmin was assigned to a user, including the OU used in step 6.c, is displayed.
- For the RMA, open the relationship list and view the properties of a relationship.
- For the AO Facility, the Administration and Operation window is displayed and no error messages are shown. The Components list in the navigation pane contains the Console entry.