Starting a remote WebSphere Application Server

Use the workbench to start a remote WebSphere® Application Server running on a Windows or Linux® operating system. You can choose to use an operating system or Secure Shell (SSH) authentication method to access the remote host that is running the server. After you provide the workbench with authentication details to the access the remote host, you can start the remote server in start or debug mode.

Before you begin

For Secure Shell (SSH) authentication method, the Linux operating systems generally support the use of SSH protocol. For Windows operating systems, however, you must install software from an independent software vendor to use SSH protocol, such as Cygwin. For details on how to generate and configure SSH key-based authentication, refer to your Secure Shell (SSH) documentation.

About this task

Important: Applicable to WebSphere Application Server traditional
Restriction:
  • Starting a remote WebSphere Application Server by using the workbench is supported only on Linux and Windows operating systems. For all the other supported operating systems that are running WebSphere Application Server, you must start the server on the remote computer, and here are your options.
    • Use the administrative console to set the correct VM parameters, for example, the debug parameter.
    • Start the WebSphere Application Server on the remote computer. After the server is started on the computer, in the Servers view of the workbench, right-click the server, and select Debug or Start to restart the server in the mode that you want.

To enable the WebSphere Application Server to start remotely:

Procedure

  1. In the Servers view, double-click the WebSphere Application Server you want to modify. The server editor opens.
  2. Click the Overview tab.
  3. In the Host name field under the General Information section, specify the fully qualified domain name server (DNS) name or IP address of the remote host machine where the server is running.
  4. In the Application server name field, under the Server section, specify the logical name for the remote application server. For WebSphere Application Server, the logical name is unique and assigned to a server that distinguishes it from all other server instances within the node. This server name must already be created in the remote application server and its default setting is server1.
  5. Under the Remote Server Settings section, select the Enable the server to start remotely check box.
  6. Select whether your remote server is installed on a Windows or Linux operating system.
    Note: Remote server start uses RXA. For more information on RXA and RXA limitations for Windows and Linux, see Requirements for using Remote Execution and Access (RXA).
  7. In the Server profile path field, enter the location of the server profile. A profile is the set of files that define the runtime environment of a WebSphere Application Server.
    Here are examples of how to specify the path to the server profile, which depends on the operating system that is running the remote server; and for Windows operating system depends if you are going to select (in the next step) Operating system authentication or Secure Shell (SSH) as the logon method to access the remote host.
    This graphic is a Linux icon. On Linux: /opt/<install_directory>/profiles/<profileName>
    Important: You must have full access to the WebSphere Application Server (and the paths) on Linux systems, with read, write, and run authority. It is not sufficient to have authority to start and stop the server, or read and write access to specific files.
    This graphic is a Windows icon. On Windows:
    • Operating system authentication: <x>:\<install_directory>\profiles\<profileName>
    • Secure Shell (SSH): /cygdrive/<x>/<install_directory>/profiles/<profileName>
      Tip: If you choose to use Cywin for your SSH protocol, you must prefix with /cygdrive/ followed by the drive letter; and use forward slashes (/) as the separator for the path.
    <install_directory>
    The directory where WebSphere Application Server is installed.
    <profileName>
    The name of the WebSphere Application Server profile. For example, the Installation Manager of this product creates a WebSphere Application Server v7.0 profile, which is assigned a default role with the following naming convention: was70profile1
    <x>
    The drive letter of the operating system where the profile of the WebSphere Application Server is located, such as C or D
  8. Under the Select a logon method to access the remote host section, there are two options:
    • Select the Operating system authentication option, if you want to use a logon credential method of an operating system to access the remote server. If you select this option, enter the user name and password for the operating system that is running on the remote host.
    • Select the Secure Shell (SSH) option, if you want to use an SSH key-based authentication method to access the remote server. If you select this option, complete the following steps:
      1. In the Private key file field, specify the location of the private key file. The default file name is id_rsa and a copy of this file must be available in the machine where the workbench is installed.
      2. In the User name field, specify the user name to the remote computer, which contains an account that is configured with the SSH key-based authentication.
      3. In the Passphrase field, specify the passphrase that is generated with the private key file. Typically, the passphrase is at least 16 characters long. If no passphrase is generated with the private key file, leave this field empty.
  9. Type Ctrl-S to save the server configuration.
  10. Close the editor.
  11. In the Servers view, right-click the server.
    There are two options to start the server, depending on which mode you want to run the server:
    • Start
    • Debug