IBM Support

PM04190: CONFIGENGINE SCRIPT 'DEPLOY-PORTAL-MASHUP-UI' FAILS IN A CLUSTER ENVIRONMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The 615 update/install was successful, but the ConfigEngine
    script
    'deploy-portal-mashup-ui' failed with the following exception:
    
    ==========================
      [wsadmin] WASX7023E: Error creating "SOAP" connection to host
    "my.dmgr.host"; exception information:
    com.ibm.websphere.management.exception.ConnectorNotAvailableExce
    ption:
    com.ibm.websphere.management.exception.ConnectorNotAvailableExce
    ption: ADMC0016E: The system cannot create a SOAP connector to
    connect to host my.dmgr.host at port 10033.
      [wsadmin] WASX7213I: This scripting client is not connected to
    a server process; please refer to the log file
    /opt/IBM/WebSphere/AppServer/profiles/wp_profile/logs/wsadmin.tr
    aceout for additional information.
      [wsadmin] WASX8011W: AdminTask object is not available.
      [wsadmin] WASX7303I: The following options are passed to the
    scripting environment and are available as arguments that are
    stored in the argv variable:
    "[/opt/IBM/WebSphere/PortalServer/base/wp.mmi.deploy/config/
    templates,
    /opt/IBM/WebSphere/PortalServer/base/wp.mmi.deploy/config/Ma
    shupTemplate.zip,
    /opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/co
    nfig/work/was]"
      [wsadmin] vp :
      [wsadmin] WASX7017E: Exception received while running file
    "/opt/IBM/WebSphere/PortalServer/base/wp.mmi.deploy/config/t
    emplates/importMashupTemplate.jacl"; exception information:
    com.ibm.bsf.BSFException: error while eval'ing Jacl expression:
      [wsadmin] EJPXD0015W: The scripting client could not connect
    to the portal.
      [wsadmin]     while executing
      [wsadmin] "$Portal login $PortalAdminId $PortalAdminPwd"
    Target finished: action-install-mashup-template-wp.mmi.deploy
    ==========================
    

Local fix

Problem summary

  • ConfigEngine script 'deploy-portal-mashup-ui' fails in cluster
    

Problem conclusion

  • Updated wp.mmi.deploy_cfg.xml to reference the correct hostname
    and port in cluster.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM04190

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-29

  • Closed date

    2010-01-04

  • Last modified date

    2010-01-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBSPHERE PORTA

  • Fixed component ID

    5724E7600

Applicable component levels

  • R61C PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 January 2010