How to Reset Verastream Management Server

  • 7021570
  • 07-Jan-2011
  • 24-May-2018

Environment

Verastream Host Integrator version 7.0 or higher

Situation

Under certain circumstances, such as lost or forgotten administrative credentials, you may want to reset the configuration of the Verastream Management Server component, rather than uninstall and reinstall the entire Verastream Host Integrator (VHI) product. This technical note describes how to reset the management server.

What is Management Server?

Verastream Management Server is a component of Verastream Host Integrator that provides support for the following features:

  • Administrative Console
  • Session Server load distribution domains (as described in KB 7021566)
  • Authentication and authorization security (as described in KB 7021567)
  • Web Services Explorer (beginning in version 7.1)
  • Session pool scheduling

The management server does not store other session server configuration including deployed models, pools, model variable lists, etc.

Why Reset?

Resetting the management server may be appropriate under one of the following circumstances:

  • The management server "admin" administrative password has been forgotten. This password is set during installation, or changed in Administrative Console.
  • The management server does not remain started due to corrupted configuration, which is identified by an error in the Attachmate/Verastream/ManagementServer/logs/server.log file, such as the following:
com.attachmate.integration.container.impl.ContainerMain - Error starting Verastream Server Container
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'permissionMgrDatastoreMgr' defined in URL [file:/C:/Program%20Files/Attachmate/Verastream/ManagementServer/services/authorization/META-INF/service-ctx.xml]: ...

or:

com.attachmate.container.impl.ContainerMain - Error starting Verastream Server Container org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'permissionMgrMBean'
  • A management server was offline when it was removed from a multi-server management cluster. Later, when the management server is online again, it needs to re-join the cluster. This situation is identified by the following symptoms:
    • In Administrative Console, when connected to the management server, the other management server(s) in the cluster appear to be offline, even though they are running and reachable.
    • If management server replication logging is configured for warn, info, or trace (in the ManagementServer/sevices/directory/META-INF/log4j-directory.xml file, in the com.attachmate.vms.directory.replication logger node, as described in KB 7021322), the following warning message is written in the Attachmate/Verastream/ManagementServer/logs/server.log file:
WARN [replication]: Several login attempts have failed to server at address <host name>/<IP address>. This usually indicates that this management server erroneously thinks it is part of a remote cluster and needs to be reset or the remote management server needs to be removed from this cluster.
  • After upgrading VHI to version 7.6 on the IBM AIX platform, the session server does not remain running and creates core dump files (caused by management cluster certificates originally generated by version 7.1.x).

Impacts of Reset

IMPORTANT! Resetting the management server will delete the following configuration in Administrative Console:

  • Authentication directory servers (in Management > Directories)
  • Authorization users and groups (in Management > Authorization)
  • Session server load distribution domains
  • Session pool start/stop schedules (in pool properties)
  • Session server registration with the management server
  • Host Emulator server
  • Administrative password (For the username admin, the password is reset to secret for VHI 7.7 and earlier, or secretpassword for VHI 7.7 SP1 and later.)

If you are using any of the above features, you will need to re-configure them after reset as directed in the procedure below. Note: All other session server configuration remains intact, including deployed models, pools, model variable lists, etc.

Resolution

The management server reset procedure varies depending on whether you have a Single-Server Environment or Multi-Server Environment.

Note: See Impacts of Reset above.

Single-Server Environment

If your Verastream Host Integrator installation environment consists of a single system (with both management server and session server components installed), use the following steps to reset the management server:

  1. Stop the "Verastream Host Integrator Session Server" service using one of the following methods.

Windows:

    • Use the Services or Computer Management utility (in Control Panel > Administrative Tools)
- or -
    • Open a Command Window as an administrator, cd to C:\Program Files\Attachmate\Verastream\HostIntegrator\bin\services\SessionServer, and run Stop Session Server.bat.

UNIX: Run /opt/attachmate/verastream/hostintegrator/bin/atstart -stop server.

  1. Unregister the session server from the management server by running the installed resetsessionserver script:

Windows: C:\Program Files\Attachmate\Verastream\HostIntegrator\bin\resetsessionserver.bat

UNIX: /opt/attachmate/verastream/hostintegrator/bin/resetsessionserver.sh

After completing this step, the session server configuration remains intact (deployed models, session pools, etc.).

  1. Make sure the Verastream Management Server service is also stopped:

Windows:

    • Use the Services or Computer Management utility (in Control Panel > Administrative Tools)
- or -
    • Open a Command Window as an administrator, cd to C:\Program Files\Attachmate\Verastream\HostIntegrator\bin\services\MgmtServer, and run Stop Management Server.bat.

UNIX: Run /opt/attachmate/verastream/hostintegrator/bin/atstart -stop mgmtserver.

  1. Reset the management server configuration by running the resetserver script:

Windows: C:\Program Files\Attachmate\Verastream\ManagementServer\bin\resetserver.bat

UNIX: /opt/attachmate/verastream/managementserver/bin/resetserver.sh

Note: This step will delete any configured authentication directory servers, authorization users and groups, session server load distribution domains, and session pool schedules. Also, the administrative password is reset to secret (VHI 7.7 and earlier), or secretpassword (VHI 7.7 SP1 and later).

  1. Start the management server service using one of the following methods:

Windows:

    • Use the Services or Computer Management utility (in Control Panel > Administrative Tools)
- or -
    • Open a Command Window as an administrator, cd to C:\Program Files\Attachmate\Verastream\HostIntegrator\bin\services\MgmtServer, and run Start Management Server.bat.

UNIX: Run /opt/attachmate/verastream/hostintegrator/bin/atstart -start mgmtserver.

Note: When the management server is started following reset, it automatically generates a new self-signed certificate and keystore.

  1. Start the session server service using one of the following methods:

Windows:

    • Use the Services or Computer Management utility (in Control Panel > Administrative Tools).
- or -
    • Open a Command Window as an administrator, cd to C:\Program Files\Attachmate\Verastream\HostIntegrator\bin\services\SessionServer, and run Start Session Server.bat.

UNIX: Run /opt/attachmate/verastream/hostintegrator/bin/atstart -start server.

  1. Run the Administrative Console application (on Windows). When connecting to the management server, enter the username admin and default password secret (VHI 7.7 and earlier), or secretpassword (VHI 7.7 SP1 and later).
  2. To change the "admin" password:
    1. To display the Management Server Explorer view, click Perspective > Management > Servers.
    2. Right click Management Cluster, click Change Admin Password, and enter the old and new passwords.
  3. Re-register the session server with the management server:
    1. If the Session Server Explorer view is not visible, click Perspective > Host Integrator > Session Servers.
    2. Right click Servers, click Add Session Server, and enter your server name.

Note: After completing this step, the session server instance will have a reference to the certificate created by the management server in step 5.

  1. If you use Host Emulator (for testing, demonstration, or training purposes):
    1. To display the Host Emulator Server Explorer view, click Perspective > Host Integrator > Host Emulator.
    2. Right click the top-level Host Emulator Servers node, click Add Host Emulator Server, and enter the server name.
  2. Re-configure the following:
    1. Any desired Load Distribution Domains, including weight and priority configuration. For more information, see KB 7021566.
    2. Any desired session pool schedules (in pool properties).
    3. Any directory servers (in Management > Directories) and authorization users and groups (in Management > Authorization). For more information, see Technical Note 10110.

Multi-Server Environment

For multiple-server environments (using a session server load distribution domain or management server cluster for failover), follow the above procedures for the Single-Server Environment with the following modifications:

  • If a single management server is failing in a multi-server management cluster, remove it from the cluster:
    1. In Administrative Console, to display the Management Server Explorer view, click Perspective > Management > Servers.
    2. Right click the offline server and click Remove.
  • Repeat steps 1 and 2 for each session server in the environment.
  • After completing steps 3 through 6 for each server, re-join each management server with the cluster:
    1. In Administrative Console, connect to the cluster.
    2. To display the Management Server Explorer view, click Perspective > Management > Servers.
    3. Right click the Management Cluster, and click Add Management Server.
    4. You will need to enter the username and password credentials from step 7 or 8.
  • Complete steps 9 through 11 for the first server. You may be able to skip them for subsequent servers as this data is automatically replicated between online management servers in the cluster.

Additional Information

Legacy KB ID

This article was originally published as Attachmate Technical Note 10114.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.