Prepare the WAS Deployment Manager on AIX


Prerequisites

  1. Prepare the AIX OS
  2. Prepare the primary node on AIX


Prepare the WAS Deployment Manager

If you are creating the dmgr profile on the same server that contains the WebSphere Portal binaries and the same WAS installation, then you can skip the step about installing or upgrading the dmgr

  1. Install WAS ND or use the CIP to upgrade an existing installation that you will use for cluster...

      cd_root/AIX/architecture/ifpackage/WAS/install

  2. If the dmgr profile was created with the "Management" profile template, you can use the existing dmgr profile,

    If the dmgr profile was created with the "Cell" profile template, create a default dmgr profile.

    While creating the default dmgr profile, enable administrative security. If you use the Profile Management Tool, check the enable administrative security check box. If you use the manageprofile command, add the paramter...

      -enableAdminSecurity true

    If you have a 64-bit environment, only the manageprofiles command is supported when creating profiles.

    • Create default dmgr profile using Profile Management Tool

      1. Run...

          cd WAS_HOME/bin/ProfileManagement
          ./pmt.sh

      2. Click...

          Launch Profile Management Tool | Create | Management | Next | dmgr | Next | Advanced profile creation | Next | Deploy the administrative console | Next

      3. On the Profile Name and Location panel, provide the name for the new profile and its location in the file system.

        The name and location must be unique from other existing profiles. Click Next to continue.

        To enable developer mode for this profile, select the check box...

          Create the server using the development template

        To specify that this profile is the default profile in the system, select the check box...

          Make this profile the default

      4. On the panell..

          Node, Host Names, and Cell Names

        provide the node name and TCP/IP host name for the new profile. If you plan to federate this profile, the node name must be unique from other profiles in the same management cell (under dmgr control). The host name must be a valid and reachable over the network. Enter the cell name for this dmgr. Click Next to continue.

      5. On the Administrative Security panel, select...

          Enable administrative security

        Enter values for the User name, Password, and Confirm password fields. Click Next to continue.

      6. On the Security Certificate (Part 1) panel, choose either...

        and choose either...

        • Create a new root signing certificate
        • Import an existing root signing certificate

        Click Next to continue.

      7. On the Security Certificate (Part 2) panel, either provide the new certificate information or verify the existing certificate information. Click Next to continue.

      8. On the Port Values Assignment panel, change any necessary port values and then click Next.

      9. On the Service Definition panel, specify whether or not the WebSphere Portal server in this profile is to be registered and controlled as a service. Click Next to continue.

      10. On the Profile Creation Summary panel, review the information collected by the wizard, and then click Create to create the new profile based on the supplied information.

        Remember the Administrative Console port value and the dmgr SOAP connector port values as you will need these values in the future.

        The port values presented in the summary value will be overridden by the port values used by the servers present in the configuration archive provided as part of the portal profile template. These port values will need to be adjusted after profile creation if they are in conflict with other ports on the local system.

      11. Click Finish to exit PMT.

    • Create default dmgr profile using manageprofile command 
      manageprofiles -create 
               -templatePath $WAS_HOME/profileTemplates/management 
               -hostName hostname 
               -profileName dmgr 
               -profilePath $WAS_HOME/profiles/dmgr 
               -cellName dmgrCell 
               -nodeName dmgr
               -Node
               -enableAdminSecurity true 
               -adminUserName dmgradmin 
               -adminPassword dmgrpass

  3. Collect files from the primary node and copy them to the remote dmgr:

    1. An archive or compressed file will be placed in...

        $PORTAL_HOME/filesForDmgr

      during installation; the file is called filesForDmgr.zip. Copy the filesForDmgr.zip file to the remote dmgr server.

      Another way to create filesForDmgr.zip, from the primary portal node

        ./ConfigEngine.sh enable-profiles
        ./ConfigEngine.sh package-profiles

    2. Copy to dmgr

        scp -r $PORTAL_HOME/filesForDmgr myhost:/tmp

    3. Stop the dmgr.

        cd $DMGR_PROFILE/bin
        ./stopManager.sh

    4. From dmgr, run...

        cd /tmp/filesForDmgr
        unzip filesForDmgr.zip
        tar cf - bin lib plugins profileTemplates profiles | (cd $WAS_HOME; tar xvfBp -)

      If the dmgr profile was not created in the default directory...

        AppServer/profiles/Dmgr01

      then the metadata_wkplc.xml file, located in...

        AppServer/profiles/Dmgr01/config/.repository/metadata_wkplc.xml

      in the zip file, must be copied into...

        config/.repository

      subdirectory under the dmgr profile directory.

  4. Augment dmgr profile:

      cd WAS_HOME/bin
      ./manageprofiles.sh -augment -templatePath $WAS_HOME/profileTemplates/management.portal.augment -profileName dmgr

    In this example, the profile template is installed under...

      /usr/WAS/AppServer/profileTemplates

    The existing dmgr profile is named Dmgr01 and is located under...

      /usr/WAS/AppServer/profiles/Dmgr01

  5. Start the dmgr.

      cd $DMGR_PROFILE/bin
      ./startManager.sh

  6. Verify that the WebSphere Portal administrative users and administrative group exist in the dmgr cell's user registry. If creating the administrative users and group:

    1. Click...

        Users and Groups | Manage Users | Create

    2. Type the information for the WebSphere Portal administrative users; for example wpsadmin and wpsbind, and then click Create.

    3. Click...

        Users and Groups | Manage Groups | Create

    4. Type wpsadmins as the name of the WebSphere Portal administrative group and then click Create.

    5. Click the group you just created; for example wpsadmins.

    6. Click...

        Members | Add Users

    7. Search for the users.

    8. Select the users you want to add to the group.

    9. Click Add to add the users to the group.

    10. Click Close when you are done adding users to the group.

    11. Log out of the administrative console.

  7. If there are common shortnames between the default dmgr security configuration and the LDAP server:

    1. Log on to the dmgr administrative console.

    2. Navigate to...

        Security | Global security | User account repository | Configure

    3. In the Primary administrative user name field, alter the user ID so that is using the full distinguished user name. For the default file user registry, the syntax is...

        uid=userID,o=defaultWIMFileBasedRealm

      for example...

        uid=wpadmin,o=defaultWIMFileBasedRealm

    4. Click Apply.

    5. Enter the password for the user and then confirm the password.

    6. Save all changes.

    7. Log out of the administrative console.


Parent

Set up a cluster on AIX


Previous

Prepare the primary node on AIX


Next topic

Prepare to create the cluster on AIX


Related

Start and stop servers, dmgrs, and node agents


+

Search Tips   |   Advanced Search