Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
9 replies Latest Post - ‏2012-12-14T09:59:00Z by gas
SystemAdmin
SystemAdmin
37422 Posts
ACCEPTED ANSWER

Pinned topic Issue creating profile for Clustered Node WAS 6.1

‏2012-12-13T15:39:32Z |
Hi

1. I am creating a new Clustered Environment with two WebSphere App Servers. <v 6.1.0.23> on AIX 6.1.

cisweb03 (Dmgr+AppSrv01)
cisweb04 (AppSrv01) This will be federated with the Dmgr (cisweb03)

2. The cisweb03 is setup with DMGR and AppSrv01 and is working fine. The response file I used for this was as follows..
root@cisweb03:> cat responsefile.ClaimsCell.txt
-OPT silentInstallLicenseAcceptance="true"
-OPT disableOSPrereqChecking="true"
-OPT installType="installNew"
-OPT feature="noFeature"
-OPT installLocation="/products/ibm/was61"
-OPT profileType="cell"
-OPT PROF_enableAdminSecurity="false"
-OPT PROF_adminUserName=
-OPT PROF_adminPassword=
-OPT PROF_dmgrProfileName=dmgr
-OPT PROF_appServerProfileName=appSrv01
-OPT PROF_profilePath="/configs/was61"
-OPT PROF_hostName=cisweb03.healthextras.local
-OPT PROF_nodeName=cisweb03DmgrNode
-OPT PROF_appServerNodeName=cisweb03Node
-OPT PROF_cellName=ClaimsCell
#-OPT PROF_defaultPorts="true"
#-OPT PROF_validatePorts="true"
-OPT PROF_startingPort=30000
-OPT PROF_nodeStartingPort=31000

3. The cisweb04 is the one giving me the issues. Even though its installing correctly. Its not creating the AppSrv01 profile. The response file for the Node Install is as follows.
-OPT silentInstallLicenseAcceptance="true"
-OPT installType="installNew"
#-OPT createProfile="true"
-OPT profileType="custom"
-OPT feature="noFeature"
-OPT PROF_isDefault="true"
-OPT installLocation="/products/ibm/was61"
-OPT PROF_profilePath="/configs/was61/appSrv01"
-OPT PROF_dmgrHost="cisweb03.healthextras.local"
-OPT PROF_dmgrPort="30003"
#-OPT PROF_dmgrAdminUserName=
#-OPT PROF_dmgrAdminPassword=
-OPT PROF_enableAdminSecurity="false"
-OPT PROF_profileName=appSrv01
-OPT PROF_hostName="cisweb04.healthextras.local"
-OPT PROF_nodeName="cisweb04Node"
-OPT PROF_startingPort=31000
#-OPT PROF_portsFile="/media/WAS61/WAS/portdef.props"
  1. Custom Node Federation
-OPT PROF_federateLater="false"
I tried with different profile configurations but its not creating the appSrv01 profile.

Please let me know if you have a solution for this.
Thanks
Kristy
Updated on 2012-12-14T09:59:00Z at 2012-12-14T09:59:00Z by gas
  • gas
    gas
    888 Posts
    ACCEPTED ANSWER

    Re: Issue creating profile for Clustered Node WAS 6.1

    ‏2012-12-13T16:13:43Z  in response to SystemAdmin
    Hi,

    What are the error messages? We will not be able to help you, if you won't provide any error info.

    You should have profile creation log in the following directory:

    /products/ibm/was61/logs/manageprofiles
    ther eshould be appSrv01_create.log

    Check errors there.

    Gas
    • SystemAdmin
      SystemAdmin
      37422 Posts
      ACCEPTED ANSWER

      Re: Issue creating profile for Clustered Node WAS 6.1

      ‏2012-12-13T16:30:05Z  in response to gas
      Thanks Gas,

      Sure, I will get the error logs for you.
      Also, can you please tell me if anything is missing or needs to be tweaked in the Responsefile.

      -Kristy
      • SystemAdmin
        SystemAdmin
        37422 Posts
        ACCEPTED ANSWER

        Re: Issue creating profile for Clustered Node WAS 6.1

        ‏2012-12-13T16:40:39Z  in response to SystemAdmin
        Please find the attached logs..These logs were obtained when I was tweaking the responsefile parameters to make it work.

        -kristy

        Fail-log1

        (Dec 12, 2012 9:34:44 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallTypeDetectAction, msg1, Process Type: install
        (Dec 12, 2012 9:34:44 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallTypeDetectAction, msg1, Install Type: nonOS400
        (Dec 12, 2012 9:34:44 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallTypeDetectAction, msg1, Install Mode: silentMode
        (Dec 12, 2012 9:34:44 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasTransferOPTPropertiesWizAction, msg1, #Received OPT Properties
        #Wed Dec 12 21:34:44 EST 2012
        PROF_nodeName=cisweb04Node
        PROF_portsFile=/media/WAS61/WAS/portdef.props
        PROF_hostName=cisweb04.healthextras.local
        PROF_dmgrHost=cisweb03.healthextras.local
        PROF_cellName=ClaimsCell
        silentInstallLicenseAcceptance=true
        PROF_federateLater=false
        profileType=custom
        PROF_dmgrPort=30003
        PROF_profilePath=/configs/was61
        PROF_isDefault=true
        PROF_profileName=appSrv01
        installType=installNew
        installLocation=/products/ibm/was61
        PROF_enableAdminSecurity=false
        feature=noFeature

        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, ********************************************************************************
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Starting a new installer run
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, ********************************************************************************
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Java Install Path: /media/WAS61/JDK/jre.pak/repository/package.java.jre/java/jre
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Name: AIX
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Architecture: ppc64
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Version: 6.1
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current User ID: root
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current User Home: /
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current Working Directory: /media/WAS61/WAS
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.PopulateTitleBarAction, msg1, IBM WebSphere Application Server V6.1.0.0
        (Dec 12, 2012 9:34:45 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPFileDeleteAction, msg1, Deleting file: Source: /tmp/.aix_ISMP_lock____
        (Dec 12, 2012 9:34:46 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction, err, Directory /products/ibm/was61 could not be validated as a non-existing or an empty directory.
        (Dec 12, 2012 9:34:46 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction, err, Directory /products/ibm/was61 could not be validated as a non-existing or an empty directory.
        (Dec 12, 2012 9:34:46 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction, err, com.ibm.ws.install.was.validators.WASInstallInvalidInputException: Directory /products/ibm/was61 could not be validated as a non-existing or an empty directory.
        at com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction.checkInstallLocationInput(WasSilentInstallInputValidationAction.java:481)
        at com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction.checkOptionValuesInput(WasSilentInstallInputValidationAction.java:122)
        at com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction.execute(WasSilentInstallInputValidationAction.java:70)
        at com.installshield.wizard.StandardWizardListener.execute(StandardWizardListener.java:123)
        at com.installshield.wizard.StandardWizardListener.currentBeanChanged(StandardWizardListener.java:106)
        at com.installshield.wizard.Wizard$RunThread.run(Wizard.java:1569)

        (Dec 12, 2012 9:34:46 PM), Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process failed.
        (Dec 12, 2012 9:34:46 PM), Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=1
        (Dec 12, 2012 9:34:46 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED
        Fail log-2
        _____________________________________

        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallTypeDetectAction, msg1, Process Type: install
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallTypeDetectAction, msg1, Install Type: nonOS400
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallTypeDetectAction, msg1, Install Mode: silentMode
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasTransferOPTPropertiesWizAction, msg1, #Received OPT Properties
        #Wed Dec 12 21:27:14 EST 2012
        PROF_nodeName=cisweb04Node
        createProfile=true
        PROF_portsFile=/media/WAS61/WAS/portdef.props
        PROF_hostName=cisweb04.healthextras.local
        PROF_dmgrHost=cisweb03.healthextras.local
        PROF_cellName=ClaimsCell
        silentInstallLicenseAcceptance=true
        PROF_federateLater=false
        profileType=custom
        PROF_dmgrPort=30003
        PROF_profilePath=/configs/was61
        PROF_isDefault=true
        PROF_profileName=appSrv01
        installType=installNew
        installLocation=/products/ibm/was61
        PROF_enableAdminSecurity=false
        feature=noFeature

        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, ********************************************************************************
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Starting a new installer run
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, ********************************************************************************
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Java Install Path: /media/WAS61/JDK/jre.pak/repository/package.java.jre/java/jre
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Name: AIX
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Architecture: ppc64
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, OS Version: 6.1
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current User ID: root
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current User Home: /
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, Current Working Directory: /media/WAS61/WAS
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.PopulateTitleBarAction, msg1, IBM WebSphere Application Server V6.1.0.0
        (Dec 12, 2012 9:27:14 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPFileDeleteAction, msg1, Deleting file: Source: /tmp/.aix_ISMP_lock____
        (Dec 12, 2012 9:27:15 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction, err, The following input options installType and createProfile can not be specified at the same time, please refer to sample response files for correct syntax.
        (Dec 12, 2012 9:27:15 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction, err, The following input options installType and createProfile can not be specified at the same time, please refer to sample response files for correct syntax.
        (Dec 12, 2012 9:27:15 PM), Process, com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction, err, com.ibm.ws.install.was.validators.WASInstallInvalidInputException: The following input options installType and createProfile can not be specified at the same time, please refer to sample response files for correct syntax.
        at com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction.checkOptionValuesInput(WasSilentInstallInputValidationAction.java:108)
        at com.ibm.ws.install.ni.ismp.actions.WasSilentInstallInputValidationAction.execute(WasSilentInstallInputValidationAction.java:70)
        at com.installshield.wizard.StandardWizardListener.execute(StandardWizardListener.java:123)
        at com.installshield.wizard.StandardWizardListener.currentBeanChanged(StandardWizardListener.java:106)
        at com.installshield.wizard.Wizard$RunThread.run(Wizard.java:1569)

        (Dec 12, 2012 9:27:15 PM), Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process failed.
        (Dec 12, 2012 9:27:15 PM), Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=1
        (Dec 12, 2012 9:27:15 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED
        • SystemAdmin
          SystemAdmin
          37422 Posts
          ACCEPTED ANSWER

          Re: Issue creating profile for Clustered Node WAS 6.1

          ‏2012-12-13T17:19:41Z  in response to SystemAdmin
          1. Can you modify the response file and give it to me so I can run it on cisweb04 ( NODE).
          2. Also can you tell me if the profile directory appSrv01 needs to be manually created under /configs/was61/appSrv01.
          -OPT silentInstallLicenseAcceptance="true"
          -OPT installType="installNew"
          #-OPT createProfile="true"
          -OPT profileType="custom"
          -OPT feature="noFeature"
          -OPT PROF_isDefault="true"
          -OPT installLocation="/products/ibm/was61"
          -OPT PROF_profilePath="/configs/was61/appSrv01"
          -OPT PROF_dmgrHost="cisweb03.healthextras.local"
          -OPT PROF_dmgrPort="30003"
          #-OPT PROF_dmgrAdminUserName=
          #-OPT PROF_dmgrAdminPassword=
          -OPT PROF_enableAdminSecurity="false"
          -OPT PROF_profileName=appSrv01
          -OPT PROF_hostName="cisweb04.healthextras.local"
          -OPT PROF_nodeName="cisweb04Node"
          -OPT PROF_startingPort=31000
          #-OPT PROF_portsFile="/media/WAS61/WAS/portdef.props"
          1. Custom Node Federation
          -OPT PROF_federateLater="false"
          • SystemAdmin
            SystemAdmin
            37422 Posts
            ACCEPTED ANSWER

            Re: Issue creating profile for Clustered Node WAS 6.1

            ‏2012-12-13T18:41:40Z  in response to SystemAdmin
            Gas, can you please help with this.

            Thanks
            Kristy
          • gas
            gas
            888 Posts
            ACCEPTED ANSWER

            Re: Issue creating profile for Clustered Node WAS 6.1

            ‏2012-12-13T18:50:06Z  in response to SystemAdmin
            Why dont you use GUI (profile management tool - pmt) to create profile??

            So from logs you can see that in first case there was problem with directory, in the second case syntax was invalid.

            Remember always, first install binaries then create profiles. Then you have much better control, than when create profiles during installation.

            Use something like this to create custom profile:

            c:\WebSphere\AppServer\bin\manageprofiles.bat -response responsefile.txt

            Contents of response file:

            create
            profileName=Custom01
            profilePath=profile_root
            templateParh=\IBM\WebSphere\AppServer\profileTemplates\managed
            nodeName=CustomNode01
            cellName=CustomNodeCell01
            hostName=myhost.mycity.mycompany.com
            dmgrHost=dmgrHost
            dmgrPort=dmgrPort
            startingPort=31000

            Check this page for details :
            http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_manageprofiles.html
            • SystemAdmin
              SystemAdmin
              37422 Posts
              ACCEPTED ANSWER

              Re: Issue creating profile for Clustered Node WAS 6.1

              ‏2012-12-13T19:15:38Z  in response to gas
              Thanks Gas,

              1. I believed that we needed xwindows to be set up to run the PMT and the SA doesnt want that. Please let me kmow if that is false.

              2. For the DMGR profile response file do you think the naming convention is right or is there something wrong.

              3. I will try installing the CORE ONLY first and once its complete I will add the profile (AppSrv).

              4. Also can you tell me should I create the profile as appSrv01 or appSrv02 on cisweb04 since the Dmgr(cisweb03) already has the appSrv01 created.

              Thanks
              Kristy
              • SystemAdmin
                SystemAdmin
                37422 Posts
                ACCEPTED ANSWER

                Re: Issue creating profile for Clustered Node WAS 6.1

                ‏2012-12-14T02:27:55Z  in response to SystemAdmin
                Try use GUI to create the profiles, you can run XWindow on your PC with XManager

                On AIX:

                #export Display=<your_ip>:sessionID
              • gas
                gas
                888 Posts
                ACCEPTED ANSWER

                Re: Issue creating profile for Clustered Node WAS 6.1

                ‏2012-12-14T09:59:00Z  in response to SystemAdmin
                >1. I believed that we needed xwindows to be set up to run the PMT and the SA doesnt want that. Please let me kmow if that is false.

                As R36 wrote, you need some xmanager on local machine (e.g. xming), then export display on server. Sometimes it might be required to create tunnel for xwin port (for example using ssh).

                > 2. For the DMGR profile response file do you think the naming convention is right or is there something wrong.
                Looks ok. It is usually by convention something like dmgr0x (e.g. dmgr01), in case you would like to have more than one dmgr on host. It may also contain some env identification name, like TSTDmgr, UATDmgr. Really depends on your requirements and conventions used in your company.
                One thing - I see you used ClaimsCell as a cell name - this might suggest that whole cell is only for your claims related application or applications. If thats true, thats fine. But usually you will have many different apps in cell, so naming it in relation with particular app or functionality might be misleading.

                > 3. I will try installing the CORE ONLY first and once its complete I will add the profile (AppSrv).
                If you already have cell profile (in fact thats 2 profiles - dmgr and appserv) on one node, you need profile on other nodes (I dont know how many nodes you want to create).
                If you just plan to make clusters across nodes, the best would be to use Custom profile (as it creates empty node, that can be automatically federated).
                If you want to have stand alone servers on separate nodes, you may create default AppServ profile, but then you will need to federate it to dmgr manually using addNode.sh script.

                > 4. Also can you tell me should I create the profile as appSrv01 or appSrv02 on cisweb04 since the Dmgr(cisweb03) already has the appSrv01 created.
                It doesnt matter. Profile name is not important, you may have same profile names on many nodes. Key item is NodeName, which must be different on each node. I would rather not name it AppSrv0x, as it suggests standalone server profile, but rather something like Node0x, prefixNode01 (again depends on your naming conventions).

                Gas