Prepare the WAS Deployment Manager on Solaris

WebSphere Portal provides a customized installation package (CIP) that includes IBM WAS Network Deployment and all required maintenance packages. Use the supplied discs to install WAS Network Deployment on a dedicated system.


Prerequisites


Prepare the Solaris OS
Prepare the primary node on Solaris
Tune the servers

To prepare the WAS Deployment Manager:

If you are creating the Deployment Manager 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 Deployment Manager and you can skip the step about collecting files if the dmgr is on a remote server.

  1. Install WAS Network Deployment or use the CIP to upgrade an existing installation that you will use for cluster. Run the following command: cd_root/Solaris/architecture/ifpackage/WAS/install, where cd_root is the root directory of the disc and architecture is the system's processor architecture.

  2. You can either use an existing Deployment Manager profile or you can choose one of the following options to create a default dmgr profile:

    If you are using an existing Deployment Manager profile, the profile must have been created with the "Management" profile template and not the "Cell" profile template. If profile was created with the "Cell" profile template, follow the instructions to create a default Deployment Manager profile.

    While creating the default Deployment Manager 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 -enableAdminSecurity true parameter to the command line. If you have a 64-bit environment, only the manageprofiles command is supported when creating profiles.

    Method Steps
    Profile Management Tool To use the Profile Management Tool:

    1. Run the ./pmt.sh command from the WAS_HOME/bin/ProfileManagement directory.

    2. Click Launch Profile Management Tool.

    3. Click Create to create a new profile.

    4. On the Environment Selection panel, select Management, and then click Next.

    5. Select Deployment Manager as the server type and then click Next.

    6. Select the Advanced profile creation radio button and then click Next.

    7. Check the Deploy the administrative console check box and then click Next.

    8. 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.

        You can also choose to select the Create the server using the development template check box to enable developer mode for this profile and the Make this profile the default check box to specify that this profile is the default profile in the system.

    9. On the Node, Host Names, and Cell Names panel, 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 Deployment Manager control). The host name must be a valid and reachable over the network. Enter the cell name for this dmgr. Click Next to continue.

    10. On the Administrative Security panel, verify the Enable administrative security checkbox is checked. Enter values for the User name, Password, and Confirm password fields. Click Next to continue.

    11. On the Security Certificate (Part 1) panel, choose either the Create a new default personal certificate or the Import an existing default personal certificate radio button and choose either the Create a new root signing certificate or the Import an existing root signing certificate radio button. Click Next to continue.

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

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

    14. 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.

    15. 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.

        You should remember the Administrative Console port value and the Deployment Manager 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.

    16. Click Finish to exit PMT.

    manageprofile command manageprofiles -create -templatePath [[Directory structure wp7|WAS_HOME]]/profileTemplates/management -hostName hostname-profileName dmgr -profilePath [[Directory structure wp7|WAS_HOME]]/dmgr -cellName dmgrCell -nodeName dmgrNode-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 the $PORTAL_HOME/filesForDmgr directory during installation; the file is called filesForDmgr.zip. Copy the filesForDmgr.zip file to the remote Deployment Manager server.

    2. Stop the dmgr.

    3. Expand the filesForDmgr.zip file into the installation root directory of the Deployment Manager; for example in the /opt/IBM/WebSphere/AppServer directory.

        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 copied into the config/.repository subdirectory under the Deployment Manager profile directory.

    4. Start the dmgr.

  4. Choose one of the following methods to augment a dmgr profile:

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

      Option Steps
      Profile Management Tool To use the Profile Management Tool:

      1. Run the ./pmt.sh command from the WAS_HOME/bin/ProfileManagement directory.

      2. Click Launch Profile Management Tool.

      3. Select Deployment Manager profile and then click Augment.

      4. On the Augment Selection panel, select Deployment Manager for Portal, and then click Next.

      5. On the Profile Augmentation Summary panel, review the information collected by the wizard, and then click Augment to augment the Deployment Manager profile with WebSphere Portal.

      6. Click Finish to exit PMT.

      manageprofiles command Run the following command from the WAS_HOME/bin directory: 

        manageprofiles.sh -augment -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/management.portal.augment
			-profileName Dmgr01

      If you have a long command, use the continuation character "/" to avoid seeing the "not found" error message.

      In this example, the profile template is installed under the /opt/IBM/WebSphere/AppServer/profileTemplates directory. The existing Deployment Manager profile is named Dmgr01 and is located under the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01 directory.

  5. Stop and restart the Deployment Manager server; see "Starting and stopping servers, dmgrs, and node agents" for information.

  6. Verify that the WebSphere Portal administrative users and administrative group exist in the Deployment Manager cell's user registry. If you need to create the administrative users and group:

    1. Click Users and Groups -> Manage Users.

    2. Click Create.

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

    4. Click Users and Groups -> Manage Groups.

    5. Click Create.

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

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

    8. Click the Members tab.

    9. Click Add Users.

    10. Search for the users.

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

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

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

    14. Log out of the administrative console.

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

    1. Log on to the Deployment Manager administrative console.

    2. Navigate to Security -> Global security.

    3. Under User account repository, click Configure.

    4. 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.

    5. Click Apply.

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

    7. Save all changes.

    8. Log out of the administrative console.


Parent

Set up a cluster on Solaris


Related tasks


Prepare to create the cluster on Solaris
Prepare a remote Web server when portal is installed on Solaris in a clustered environment
Configure WebSphere Portal to use a user registry on Solaris in a clustered environment
Prepare additional nodes on Solaris
Configure search in a cluster on Solaris
Set up multiple clusters on Solaris
Share database domains between clusters on Solaris
Start and stop servers, dmgrs, and node agents

  Fixed step 6f. Added the restriction note in step 2.


+

Search Tips   |   Advanced Search