Configuring advanced options for single server classic virtual system patterns

You can configure advanced options for single server classic virtual system patterns.

1. Enable the session persistence.
   HVWebCluster or application clusters are created with associated replication domains. Therefore, you can use the hyper text transfer protocol (HTTP) session replication. If the replication domain is defined, no resources are started or used unless session replication is configured. You can use the Enable session persistence option and then one of the following options to configure HTTP session persistence:

   Memory-memory implemented session persistence

   The HTTP session memory bit is set on all the HVWebCluster servers.

   Database implemented session persistence

   To use this option on the classic virtual system instance, the Java™ Database Connectivity (JDBC) data source must be updated on the deployment manager. You must provide valid host, port, user name, and password values. Also, the appropriate client drivers for your database, for example jars and libraries, must be installed on your WebSphere® Application Server systems. IBM® Cloud Pak System Software for Power® performs the following operations:

   • Creates a DB2® JDBC provider
   • Creates a sample DB2 data source, with dummy values for the host, port, ID, and password
   • Sets up a session manager on each HVWebCluster server to do HTTP session to the database, using the sample data source and dummy connection values

   For important information about configuring database implemented session persistence for a supported HTTP session, see the related links.

2. Enable global security.
   Using global security provides the following functions:

   • Sets the global security admin bit.
   • Uses the WIM user registry that is provided with Cloud Pak System Software for Power.
   • Uses both LTPA and BasicAuth for authentication (BasicAuth is needed for stand-alone clients).
   • Uses an SSL-allowed policy for CSIv2.
   • Turns off single signon interoperability.
   • Configures secure file transfer between the deployment manager and the node agents.
   • Enables the high availability manager to use the secure DCS channel.

   Use the global security option to configure secure messaging. Secure messaging provides the following functions:

   • Sets the security bit on the SIBus.
   • Reduces the set of users that can connect to the SIBus. Only the WebSphere Application Server ID created with the CB UI can connect. The default value for that ID is virtuser.
   • Disables the InboundBasicMessaging transport for the messaging engines.
   • Adds the virtuser ID to the sender role for foreign buses for MQLink configurations.