Configuring Domino and Portal Server federated administration

You can administer a Domino® server and an HCL Digital Experience server from the Portal Server administration user interface (UI) on the same Portal Server.

About this task

In this configuration, the Domino Web Administrator UI is embedded in the Portal administration UI. To administer both server types from one Portal administration user interface, link the Domino Web Administrator client UI to the Portal administration UI. The Domino Web Administrator UI then displays with other portal-specific user interfaces.

Procedure

  1. If you have not already done so, download the Portal 6 Update Installer (PUI) tool.
  2. Patch your Portal Server with the iFix. Apply this patch only once. If you are using Portal Server 6.0.1 or greater, you do not need to do this.
  3. After patching the Portal Server, run the access scripts to add Domino servers to the Portal administration user interface. You must run one access script for each server.
  4. Be sure to complete the procedure Enabling the Portal server for federated administration in this guide.
  5. Clear your browser's cache file.

Results

The iFix consists of a .ZIP file which includes a .jar file and a readme.txt file. The .ZIP file is contained within the database WEBADMIN.NSF.

There are two XML Access scripts. One XML Access script adds a Domino server into the Portal administration UI; one XML Access script removes a Domino server from the Portal administration UI. Each XML Access script is a single XML-based configuration file used as input for the Portal XML configuration interface tool.

Run the XML Access script once for each Domino Web administration server to be integrated into or removed from the Portal administration UI. For example, if two servers (ServerA and ServerB) should be integrated into the Portal Administration UI, point the browser to each of the two servers, obtain the addfederation.xml file from each server, and then run each file against the Portal Server. The Portal Administrator UI would then be configured to include the two Domino servers.

Note: A successful SSO configuration must exist between the Portal Server and the Domino server.

Preparing the portal server

About this task

You need to perform this procedure only one time for the Portal Server.

Procedure

  1. If you have not already done so, download the Portal Update Installer (PUI) tool. You can download the PUI from the WebSphere® Portal Support Web site.
  2. Download the file iFix.zip from any Domino server by pointing to this URL which triggers the download

    http://dominoserver/webadmin.nsf/iFix.zip

  3. Save the file, iFix.zip, locally on the Portal server.
  4. Unzip the file, and then install it. For information about installing the file, see IBM® WebSphere Portal Update Installer README in the WebSphere Portal Information Center.
  5. Access the directory PortalServerRootDirectory\config\ subdirectory, and then run this command:

    WPSconfig.bat init deploy-transformation-federation -DPortalAdminId=wpsadminid -DPortalAdminPwd=wpsadminpwd

    Note: On UNIX™ systems, use WPSConfig.sh instead of WPSConfig.bat.

Setting up Domino and Portal server federated administration

Procedure

  1. From the Portal Server, download the configuration script from this URL

    http://dominoserver/webadmin.nsf/addfederation.xml

  2. Save the file locally on the Portal server.
  3. Access the directory PortalServerRootDirectory\bin subdirectory, and then run this command:

    xmlaccess.bat -in c:\addfederation.xml -user wpsadminid -password wpsadminpwd -url localhost:10038/wps/config

    Port 10038 is the default port. If you configured the portal server to use a different port, specify the port number that you used when you configured the Portal Server.
    Note: On UNIX systems, use xmlaccess.sh instead of xmlaccess.bat.
  4. Log out and then log in.