IBM Support

LO57308: CHANGE SERVER NAMES POST INSTALL FOR LOTUS CONNECTIONS 3.0

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Change server names post install for Lotus Connections 3.0
    

Local fix

  • n/a
    

Problem summary

  • Abstract: Change server names post install for Lotus Connections
    3.0
    
    Summary:
    
    Here is the instructions:
    
    Before you begin, please note:
    - Keep a note of the original server names and their location
    (which Cluster, wich Node)
    - Note that when server names are changed. You will no longer be
    able to uninstall or add/remove features to the deployment. If
    you want to uninstall or add/remove features, please change the
    server names back to its original names. You will no longer be
    able to install fixpacks either, for you to do that, please
    change back to the old server names.
    
    1, Backup your configuration data <WAS_HOME>/bin directory
    2, Stop all Lotus Connections cluster via Integrated Solution
    Console on the DM
    3, Stop the DM process, e.g. dmgr
    4, Download ConfigScripts.zip
    5, Unzip ConfigScripts.zip and copy all files in ConfigScripts
    directory to your <was_root>/bin directory.
    6, Execute the following command under your <was_root>/bin
    directory
    Syntax:
      ws_ant[.sh] changeServerName -profileName <profileName>
    -buildfile configScripts.xml [-logfile <logfile>]
    -DoldServerName=<oldServeName> -DnewServerName=<newServerName>
    -DclusterName=<clusterName> -DnodeName=<nodeName>
    Note:
    <profileName>: the WAS profile name of the DM, e.g. Dmgr01
    <logfile>: the log file name for  the command prompt
    <oldServerName>: the original name of the server whose name you
    want to change
    <newServerName>: the new name of the server whose name you want
    to change
    <clusterName>: the cluster that holds the server member whose
    name you want to change
    <nodeName>: the node that holds the server whose name you want
    to change
    
    Example:
       ws_ant changeServerName -profileName dmgrProfile -buildfile
    configScripts.xml -logfile changeServer.log
    -DoldServerName=LCInfraCluster_server1
    -DnewServerName=LCInfraCluster_ServerMember01
    -DclusterName=LCInfraCluster
    -DnodeName=win2003r2-std-32bitNode01
    7, start the DM
    8, do a full synchronize via Integrated Solution Console on the
    DM
    9, start all LC clusters
    

Problem conclusion

  • Change server names post install for Lotus Connections 3.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO57308

  • Reported component name

    CONNECTN ACTIVI

  • Reported component ID

    5724S6800

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-23

  • Closed date

    2010-12-23

  • Last modified date

    2010-12-23

  • 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

    CONNECTN ACTIVI

  • Fixed component ID

    5724S6800

Applicable component levels

  • R300 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCYJJE","label":"Activities"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
23 December 2010