Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Preparing non-portal nodes for Member Manager security
After the cluster is created, set up non-portal node security access to the Member Manager datasource.
In some environments the cell may contain other non-portal nodes. In some cases these non-portal nodes may need access to the Member Manager datasource. This is especially important when using the default Member Manager database security or when using LDAP security with a Lookaside database.
Before performing these steps deployment manager login must be enabled to use the WebSphere Application Server short ID. Complete the following steps to provide access to the Member Manager datasource.
If you want to log in to the deployment manager administrative console using the WebSphere Application Server short ID, complete the following steps on the deployment manager machine. If you want to give all nodes in the cell access to the Member Manager database, the following steps must be performed on each non-portal node. While access to the database is not required in all setups, it is recommended to perform these steps in all cases because some configuration changes may required the use of the database:
- Ensure that the database software required for the Member Manager domain is installed. The software is installed locally on the non-portal node.
If you are using DB2 Type 2 drivers catalog the Member Manager User Registry database on the non-portal node.
- This step may be skipped if access is being set up on non-portal nodes. Create a connection for the deployment manager to the Member Manager database.
- First establish a unique datasource name for the database by setting the following property in the wpconfig_dbdomain.properties file:
wmm.DataSourceName=wmmdbDS
- Create the connection by running the following command on the cluster's primary node, from the portal_server_root/config directory, or for i5/OS, from the portal_server_root_user/config directory:
- Windows:
WPSconfig.bat connect-database-wmm
- Linux:
./WPSconfig.sh connect-database-wmm
- i5/OS:
WPSconfig.sh -profileName profile_root connect-database-wmm -DWasPassword=password
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
- Windows:
- First establish a unique datasource name for the database by setting the following property in the wpconfig_dbdomain.properties file:
- Log in to the deployment manager administrative console, and click Resources > JDBC Providers. View the resources at Cell scope by verifying the Node and Server fields are empty and click Apply.
- Click on the JDBC provider that contains the Member Manager data source.
- In the Classpath field, note the name of the environment variable specified. For example, ${ DB2_JDBC_DRIVER_CLASSPATH}.
- Select Environment > WebSphere Variables in the navigation tree.
- Select either the deployment manager or the non-portal node to filter the list of variables. Select Browse Nodes, then select either the deployment manager Node or the non-portal Node, and then click Apply.
- Click New.
- Enter the name of the variable previously specified by the JDBC provider, for example DB2_JDBC_DRIVER_CLASSPATH.
- In the Value field, enter the directory and name of the ZIP or JAR file that contains the JDBC driver class. For example: db2_install/java/db2java.zip.
- Save your changes to the deployment manager configuration.