Configuring HCL Docs profiles

After the installation of the WebSphere® Application Server, you must create the profile and cluster for each of the HCL Docs components.

About this task

Note:
  • Since the 1.0.7 release, all HCL Docs related clusters will be created automatically. You just need to create profiles and federate them into your Deployment Manager. If your environment has vestigial HCL Docs applications information, make sure to clean your deployment environment by uninstalling them and deleting all related clusters.
  • Generally, IBM® WebSphere® Application will take profile AppSrv01 as its default. When you create semantic profile names, not AppSrv01, you must ensure the profile AppSrv01 is deleted if it is not used or federated into your Deployment Manager.
  • Important: The following procedure assumes that your environment is the medium-to-large deployment that is described in the Planning section of this guide.

Procedure

  1. Launch the Profile Management Tool.
  2. In the WebSphere® Customization Toolbox window, click on the Create button.
  3. In the Environment Selection screen, select the following and click Next.

    Custom Profile

  4. At the Profile Creation Options screen, select the following and click Next:

    Advanced profile creation

  5. At the Profile Name and Location screen, specify the following parameters (take Conversion as an example):
    Table 1. Profile Name and Location parametersThis table provides suggested default values for profile name and location.

    This table provides suggested default values for profile name and location.

    Field Value
    Profile name profile name, for example, AppSrv01 as the default. The profile names must be the same for all Conversion nodes. Docs is the same.
    Profile directory Linux™ WAS_INSTALLPATH_LINUX, for example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01, with ConversionCluster_NODENAME_1, for example, DocsWin01
    Windows™ WAS_INSTALLPATH_WINDOWS, for example, C:\IBM\WebSphere\AppServer\profiles\AppSrv01 with ConversionCluster_NODENAME_1, for example, DocsWin01
  6. Click Next.
  7. At the Node and Host Names screen, specify the following parameters (take Conversion as an example):
    Table 2. Node and Host Names parametersThis table provides suggested default values for node and host names.
    Field Value
    Node name Specify the profile name in the previous step DocsProxyCluster_NODENAME_1, for example, DocsWin01
    Host name Fully qualified hostname ConversionCluster_HOSTNAME_1, for example, DocsWin01.example.com
  8. Click Next.
  9. At the Federation screen, specify the following parameters:
    Table 3. Federation parametersThis table provides suggested default values pertaining to federation.
    Field Value
    Deployment manager host name or IP DMGR_HOST, for example, DocsLab01.example.com
    Deployment manager SOAP port number 8879
    Deployment Manager Authentication - User name WASADMIN_USERNAME, for example, wasadmin
    Deployment Manager Authentication - Password WASADMIN_PASSWORD, for example, password
    Note: If you want to use the command to federate the node, refer to the example: ./addNode.sh dmgr-host-name 8879 -user wasadmin -password wasadmin -localusername wasadmin -localpassword wasadmin.
  10. Click Next.
  11. At the Security Certificate (Part 1) screen, accept the defaults. Click Next.
  12. At the Security Certificate (Part 2) screen, accept the defaults. Click Next.
  13. At the Port Value Assignment screen, accept the defaults. Click Next.
    Note: To Windows™, it is Windows Services Definition. Accept the default and click Next to ensure WebSphere® Application Server to run as a service of Windows™ and start automatically along with system restarting.
  14. At the Profile Creation Summary screen, click Create.
  15. When the process has finished uncheck the box Launch the First steps console. Click Finish.
  16. Repeat for the remaining WebSphere® 8.0 servers.