+

Search Tips   |   Advanced Search

Augment a stand-alone default profile with WebSphere Portal on Solaris


We can augment an existing IBM WebSphere Application Server default profile running in a stand-alone (non-federated) environment with IBM WebSphere Portal. The augmentation adds the WebSphere Portal configurations, applications, and application server that were saved from the baseline WebSphere Portal configuration.

Augmenting profile containing specialized application server instances installed by other products with WebSphere Portal could potentially introduce some configuration conflict. You should contact IBM before proceeding in such an environment to determine if any support limitations exist.

A valid IBM WAS default profile must exist.

The WebSphere Portal installation registers the WebSphere Portal default profile augmentation template with WAS. We can then augment existing default profiles with WebSphere Portal based on this template. Use the manageprofiles.sh to complete this profile augmentation. The portal still has the same database configuration, including the portal Administrator ID and password as the initial profile used to run the enable-profiles or replace-profiles tasks. If the initial profile was using the Derby database, a fresh copy is automatically created with the new profile. If the initial profile was configured to use a non-Derby database, then all the database domains of the new profile are identically configured. Profile augmentation does not modify the security settings that are configured for the existing profile.


Create a profile

  1. Add the repositories where the installation media exists:

    1. Open the Installation Manager and navigate to...

        File > Preferences > Repositories > Add Repositories

    2. Select Browse and navigate to the IBM WAS service repository and then click OK.

    3. Ensure all required repositories are checked.

    4. Click Test Connections.

    5. Select Apply.

    6. Select OK.

  2. On the main Installation Manager panel, select Install to begin the installation process.

    1. On the panel...

        Select packages to install

      ...select both the WAS and WebSphere Portal packages.

    2. On the panel...

        Select the fixes to install

      ...select the following fixes based on how we are accessing the repository:

        When you install WAS and WebSphere Portal together from the live repository (Passport Advantage)

        • 8.0.0.3-WS-WAS-IFPM59935
        • 8.0.0.3-WS-WAS-IFPM60670
        • 8.0.0.3-WS-WASProd-IFPM60134
        • 8.0.0.3-WS-WAS-IFPM61934

        When you install WAS and WebSphere Portal together from the local repository (DVD or downloaded eImage)

        • 8.0.0.3-WS-WAS-TFPM59935
        • 8.0.0.3-WS-WAS-TFPM60670
        • 8.0.0.3-WS-WASProd-TFPM60134
        • 8.0.0.3-WS-WAS-TFPM61934

    3. Click Next.

    4. Accept the license agreement and then click Next.

    5. Select shared resources directory and then click Next.

    6. Set Installation Directory:

      1. Select the WAS Package Group Name and then select the installation directory path.

      2. Select the WebSphere Portal Package Group Name and then select the installation directory path.

      3. Click Next.

    7. Select the translations to install and then click Next.

    8. On the panel...

        Select the features to install

      ...expand the WAS and WebSphere Portal packages

      Expand the WebSphere Portal package and deselect the feature...

        Create a new Portal Server Profile

      A full WebSphere Portal server is not currently required. We create the custom profile later.

    9. Confirm the information on the Summary panel and then click Install.

  3. To create a directory to store templates:

    1. Copy...

        PORTAL_HOME/profileTemplates/profileTemplates.zip

      ...on the primary node to the same location on the additional cluster node.

    2. Extract the profileTemplates.zip file in the same location. If any of the templates already exist in the profileTemplates directory, overwrite them.

    3. Because some files are set to read-only after the copy operation, open permissions...

        chmod -R 755 PORTAL_HOME/profileTemplates

    4. To install the copied profile template...

        cd PORTAL_HOME/profileTemplates
        ./installPortalTemplates.sh

      This task localizes the profile templates to the current environment and registers them with the pmt.sh if it exists on the server.

  4. To create a profile:

    Option Steps
    manageprofiles.sh cd WAS_HOME/bin 
    ./manageprofiles.sh -augment -templatePath 
    /opt/IBM/WebSphere/PortalServer/profileTemplates/default.portal.augment
  -profileName AppSrv01
  -cellName testCell
  -nodeName testNode
  -hostName myHost.xxx.com

    Use the continuation character "\" to avoid seeing the "not found" error message.

    In this example, the portal profile template is installed under the /opt/IBM/WebSphere/PortalServer/profileTemplates directory. The existing default profile is named AppSrv01.

  6. If you changed the default realm, replace the WAS and WebSphere Portal administrator user ID:

    1. Create a new user in the Manage Users and Groups portlet to replace the current WAS administrative user.

    2. Create a new user in the Manage Users and Groups portlet to replace the current WebSphere Portal administrative user.

    3. Create a new group in the Manage Users and Groups portlet to replace the current group.

    4. Replace the old WAS admin user ID and group ID with the new user and group...

        ./ConfigEngine.sh wp-change-was-admin-user -DWasUser=adminid -DWasPassword=foo -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid

      Provide the full DN for the newAdminId and newAdminGroupId parameters.

      This task verifies the user against a running server instance. If the server is stopped, to skip the validation...

        -Dskip.ldap.validation=true

    5. Verify the task completed successfully. Stop and restart all required servers.

    6. Replace the old WebSphere Portal admin user ID and group ID with the new user and group...

        ./ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=foo -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid

      Provide the full DN for the newAdminId and newAdminGroupId parameters.

      This task verifies the user against a running server instance. If the server is stopped, to skip the validation...

        -Dskip.ldap.validation=true

    7. Verify the task completed successfully. Stop and restart all required servers.


Parent: Create or augment profiles on Solaris