Configure the primary node to communicate with the deployment manager on i5/OS

After installing IBM WAS Network Deployment and installing WebSphere Portal on the primary node, configure the primary node and the deployment manager to communicate with each other.


Prerequisites

Installing WebSphere Portal on i5/OS on the primary node

Set up a remote database
Perform the following step to configure WebSphere Portal to communicate with the deployment manager: Collect files from the primary node and copy them to the deployment manager:

  1. Run...

      ConfigEngine.sh collect-files-for-dmgr -DWasPassword=password task, from profile_root/ConfigEngine of the primary node, to create an archive or compressed file containing all the files which need to be copied to the Deployment Manager.

      The archive or compressed file will be placed in the profile_root/filesForDmgr directory and the file will be called filesForDmgr.zip.

    • Stop the deployment manager.

    • Expand the filesForDmgr.zip file into the installation root directory of the Deployment Manager; for example this may be a subdirectory under the AppServer directory and it will contain the bin and profileTemplates directories.

      If the Deployment Manager profile was not created in the default AppServer\profiles\Dmgr01 directory, then the metadata_wkplc.xml file, located in the AppServer/profiles/Dmgr01/config/.repository\metadata_wkplc.xml directory in the zip file, must be placed into the correct Deployment Manager profile directory.

    • Start the deployment manager.


Parent topic:

Prepare the primary node on i5/OS


Previous topic:

Set up a remote database


Next topic:

Removing search collections on i5/OS


Related tasks


Configure Portal Search in a cluster on i5/OS