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

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

Before you begin

Note: Augmenting profiles that contain 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 WebSphere Application Server default profile must exist.

About this task

The WebSphere Portal installation registers the WebSphere Portal default profile augmentation template with WebSphere Application Server. You can then augment existing default profiles with WebSphere Portal based on this template. You must use the manageprofiles command 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 your initial profile was using the Derby database, a fresh copy is automatically created with the new profile. If your 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.

Complete the following steps to create a profile:

Procedure

  1. After installing or upgrading the IBM Installation Manager, complete the following steps to add the repositories where the installation media exists:
    1. Open the IBM Installation Manager and navigate to File > Preferences > Repositories.
    2. Select Add Repositories.
    3. Select Browse and navigate to the Portal-install-eimage/Setup/eimage/repository.config file and then click OK.
    4. Ensure that all required repositories are checked. Then click Test Connections to ensure that the IBM Installation Manager can successfully access the directory where the service repositories are stored.
    5. Select Apply.
    6. Select OK.
  2. On the main IBM Installation Manager panel, select Install to begin the installation process.
    1. On the Install Packages: Select packages to install panel, select both the WebSphere Application Server and WebSphere Portal packages.
    2. On the Install Packages: Select the fixes to install panel, select the following fixes based on how you are accessing the repository:
      When you install WebSphere Application Server 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 WebSphere Application Server and WebSphere Portal together from the local repository (DVD or downloaded eImage from the web-site)
      • 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 the directory where you want to store shared resources and then click Next.
    6. Complete the following steps on the Install Packages: Installation Directory panel:
      1. Select the WebSphere Application Server 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 Install Packages: Select the features to install panel, expand the WebSphere Application Server and WebSphere Portal packages to modify the features you want to install and then click Next.
      Attention: On the Install Packages: Select the features to install panel, expand the WebSphere Portal package and deselect the Create a new Portal Server Profile feature. A full WebSphere Portal server is not currently required. You create the custom profile later.
      Note: As you select the items, read the Details section for information about the selections.
    9. Confirm the information on the Summary panel and then click Install.
  3. Complete the following steps to create a directory to store templates:
    1. Copy the profileTemplates.zip file from the PortalServer_root/profileTemplates directory 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 your profileTemplates directory, overwrite them.
    3. Run the chmod -R 755 PortalServer_root/profileTemplates task to change the permissions of the files and directories, located in the PortalServer_root/profileTemplates directory, because some files are set to read-only after the copy operation.
    4. Run the ./installPortalTemplates.sh AppServer_root task from the newly created profileTemplates directory to install the copied profile template. This task localizes the profile templates to the current environment and registers them with the Profile Management Tool if it exists on your server.
  4. Complete the following steps to create a profile:
    Table 1. Running the manageprofiles task to create a profile.
    Option Steps
    manageprofiles command Run the following command from the AppServer_root/bin directory:
    ./manageprofiles.sh -augment -templatePath 
    /opt/IBM/WebSphere/PortalServer/profileTemplates/default.portal.augment
		-profileName AppSrv01
		-cellName testCell
		-nodeName testNode
		-hostName myHost.xxx.com
    Tip: If you have a long command, 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.
  5. Complete the following steps to replace the WebSphere Application Server and WebSphere Portal administrator user ID; if you change the default realm this step is needed:
    1. Create a user in the Manage Users and Groups portlet to replace the current WebSphere Application Server administrative user.
    2. Create a user in the Manage Users and Groups portlet to replace the current WebSphere Portal administrative user.
    3. Create a group in the Manage Users and Groups portlet to replace the current group.
    4. Run the ./ConfigEngine.sh wp-change-was-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword task, from the wp_profile_root/ConfigEngine directory to replace the old WebSphere Application Server administrative user ID and group ID with the new user and group.
      Important: You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId parameters.
      Additional parameter for stopped servers: This task verifies the user against a running server instance. If the server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.
    5. Verify that the task completed successfully. Stop and restart all servers.
    6. Run the ./ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid task to replace the old WebSphere Portal administrative user ID and group ID with the new user and group.
      Important: You must provide the full distinguished name (DN) for the newAdminId and newAdminGroupId parameters.
      Additional parameter for stopped servers: This task verifies the user against a running server instance. If the server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.
    7. Verify that the task completed successfully. Stop and restart all servers.