Changing a WAS configuration

 


  1. Invoke AdminConfig

  2. Get the id of the relevant node:

    set n1 [$AdminConfig getid /Node:nodename/]
    

  3. Create a server on your node by running...

    set serv1 [$AdminConfig create Server $n1 {{name servername}}]
    

    ...which writes files to...

    /opt/WebSphere/AppServer/wstemp

    Later, when an "AdminConfig save" command is invoked, the changes represented in these temporary files are transferred to the permanent configuration repository.

  4. Configure the initial state of your server:

    $AdminConfig modify $serv1 {{stateManagement {{initialState STOP}}}}
    

  5. Install an application on the server.

  6. Save the configuration changes using "$AdminConfig save"

  7. Synchronize nodes. Note that by default this occurs periodically, as long as the node can communicate with the deployment manager. To explicitly synchronize nodes:

    set Sync1 [$AdminControl completeObjectName name]
    $AdminControl invoke $Sync1 sync
    

    When the synchronization is complete, the files created in...

    /opt/WebSphere/DeploymentManager/config
    ...now exist on the nodename node, in...

    /opt/WebSphere/AppServer/config