+

Search Tips   |   Advanced Search

Install Web Content Manager into an existing Server installation on IBM i


If you initially installed the IBM WebSphere Portal Server installation, we can purchase the Content license agreement and install the IBM Web Content Manager features into your existing installation.

To install Web Content Manager into an existing Server installation:

Cluster note: In a clustered environment, complete these steps on all the nodes.

Response file note: Run the sample response file to install the Web Content Manager features on your existing Server installation. See Use response files to install for information. For IBM i edit the appropriate sample response file located in

because we can not record the response file from the operating system. We can record a response file on another operating system using the following steps when recording the response file. Ensure that you exit from the Installation Manager program to complete the recording. You must edit the response file that you recorded to add the IBM i specific parameters.

  1. Stop all the appservers.

  2. Manually update the appropriate sample response file, located in...

      setup_root/responsefiles/iseries directory

    Replace the following lines in the sample response files if you installed WAS and WebSphere Portal from the live repository (Passport Advantage):

      Existing lines in the response file

      • <offering id='8.0.0.3-WS-WAS-TFPM59935' version='8.0.3.20120309_1201' profile='IBM WAS Network Deployment V8.0' features='-'/>

      • <offering id='8.0.0.3-WS-WAS-TFPM60670' version='8.0.3.20120319_1949' profile='IBM WAS Network Deployment V8.0' features='-'/>

      • <offering id='8.0.0.3-WS-WASProd-TFPM60134' version='8.0.3.20120312_1656' profile='IBM WAS Network Deployment V8.0' features='-'/>

      • <offering id='8.0.0.3-WS-WAS-TFPM61934' version='8.0.3.20120409_1230' profile='IBM WAS Network Deployment V8.0' features='-'/>

      Replace with

      • <offering id='8.0.0.3-WS-WAS-IFPM59935' version='8.0.3.20120424_1630' profile='IBM WAS Network Deployment V8.0' features='-'/>

      • <offering id='8.0.0.3-WS-WAS-IFPM60670' version='8.0.3.20120428_0856' profile='IBM WAS Network Deployment V8.0' features='-'/>

      • <offering id='8.0.0.3-WS-WASProd-IFPM60134' version='8.0.3.20120425_1032' profile='IBM WAS Network Deployment V8.0' features='-'/>

      • <offering id='8.0.0.3-WS-WAS-IFPM61934' version='8.0.3.20120417_1256' profile='IBM WAS Network Deployment V8.0' features='-'/>

    Use the Installation Manager command-line tool imutilsc from the installation tools directory to encrypt the WebSphere Portal administrator password string. Enter the encrypted password in the response file.

    imutilsc encryptString stringToEncrypt
    

    If installing on a different computer, copy the updated response file to the response file directory on that computer.

    We can record a response file using a different operating system , We can record a response file using a different operating system. After recording the response file on the other operating system, modify the file for IBM i. Then copy the response file to the IBM i server.

  3. If the repository URL requires authentication, use imutilsc.sh to create a keyring file store for credentials.

    The keyring file stores the credentials required for the repositories. The Installation Manager command-line tool imutilsc is available from the installation tools directory.

    imutilsc saveCredential -url repository_URL -userName credential_userName
     -userPassword password -keyring keyring_file [ -password keyringfile_password ]
     [ -proxyHost proxy_host -proxyPort proxy_port
      [ -proxyUsername proxy_username -proxyUserPassword proxyuser_password ]
      [ -useSocks ] ]
     [ -verbose ]
    

    If installing on a different computer, copy the keyring file to that computer.

  4. Install WebSphere Portal and IBM WAS run...

      imcl -acceptLicense -input /path/to/response.xml -log /path/to/log/files

    To use your repository keyring file...

      -keyring /path/to/keyring -password keyringfile_password

  5. After the installation successfully completes, stop and restart the appropriate servers to propagate the changes. For specific instructions, see Start and stop servers, dmgrs, and node agents.

  6. Complete the following steps if you created multiple profiles outside of the Installation Manager:

    For each profile.

      cd WP_PROFILE/ConfigEngine
      ConfigEngine.sh enable-wcm -DWasPassword=foo

    1. Stop and restart the appropriate servers to propagate the changes. For specific instructions, see Starting and stopping servers, dmgrs, and node agents.


Parent: Install on IBM i