Configuring advanced messaging for databases

You can enable messaging when configuring the advanced options on a cluster classic virtual system pattern.

Before you begin

To enable messaging, there are additional configuration options you must specify. You can use these options to start and use clustered messaging engines or to use a sample authentication alias for databases. For more information about configuring advanced options for cluster classic virtual system patterns, see the Related tasks section.

About this task

You must complete some additional configuration tasks to work with clustered messaging engines or to configure a sample authentication alias for databases, in certain WebSphere® Application Server configurations.

Procedure

Use the IBM® Cloud Pak System Software for Power® sample authentication alias.
The sample authentication alias can be used by the messaging engines for databases other than Derby. If you use the Cloud Pak System Software for Power messaging recommendations and an enterprise database such as DB2® or Oracle, perform the following steps:
1. Create the appropriate Java™ Database Connectivity (JDBC) driver and data source for your database.
2. Update the sample authentication alias for the database provided by Cloud Pak System Software for Power to contain the correct credentials to your database.
3. Change the messaging engine and SIBus configuration to use the new data source, where the updated authentication alias is used with this data source.
Use a database server.
To properly start and use clustered messaging engines, a database server is required. You can use the Derby database server that is included with WebSphere Application Server. Cloud Pak System Software for Power provides configuration, the definition of a Derby database server included with WebSphere Application Server, which runs on the deployment manager of the classic virtual system pattern. A JDBC provider and data source point to a Derby network server. This server is started from the deployment manager node, from the Derby installation under the WAS installation root. Cloud Pak System Software for Power provides this function for messaging to minimize later configuration. To start Derby from the deployment manager before starting the messaging cluster, you can update the Derby configuration for remote connections. To update this process, perform the following steps:
1. Edit the <WAS_HOME>/derby/derby.properties file.
  Uncomment the following line:
```
#derby.drda.host=0.0.0.0
```
2. Start the Derby network server.
  To start this server, from the <WAS_HOME>/derby/bin/networkServer/ directory run the following command:
```
startNetworkServer.sh | .bat
```
3. Start the Derby database server on the deployment manager node.

Results

You have configured the cluster classic virtual system pattern to start and use clustered messaging engines or to use a sample authentication alias for databases.

What to do next

When you have configured messaging, you can configure the advanced options for the cluster classic virtual system pattern you are editing.