WebSphere Connectors

Our WebSphere support includes project deployment management as well as application server control features. 

WebSphere requires a MyEclipse Blue or Bling subscription.


1. WebSphere Project Deployment

MyEclipse with WebSphere support provides advanced WebSphere project deployment management as well as application server control features. Deploying projects to and controlling a WebSphere server is the same as with any other MyEclipse application server connector. However, WebSphere connectors have a few extra features. 

2. WebSphere Server Connector

When setting up a WebSphere connector, you add the WebSphere instance, and then, you can make further configuration changes using the server configuration editor. See Using MyEclipse Application Servers for general steps for setting up and using a server connector. The WebSphere differences are presented in the sections below. 

2.1 WebSphere-specific JRE

When selecting the configured JRE, MyEclipse identifies and configures the JDK that is part of your WebSphere installation.

Runtime configuration

When configuring a WebSphere connector, the wizard provides a page for you to select from a list of profiles found in your installation folder and enter security credentials (if security is enabled), so MyEclipse can connect to the profile.

Adding a server instance

2.2 Additional Connector Configuration

When setting up a WebSphere connector, you add the WebSphere instance, and then you can make further configuration changes using the Server Configuration editor.

  1. Double-click the server in the Servers view to open the Server Configuration editor.

    WebSphere Server Configuration editor
    Note: Protocol settings shown above are available in MyEclipse 2015 CI 13 and later.
  2. In the Advanced publishing settings, you can change the deployment mode. See Deployment Modes for a description of each.
  3. To set server launch configurations such as arguments and classpath settings, click the Open launch configuration link.

    Launch configuration properties

    3. Cloning a WebSphere Server Configuration

    From the Servers view, you can create a configuration archive (CAR) file to clone an application server configuration from one instance of WebSphere to another. Configuration archives can be exported and imported for WebSphere 6.0 and above. For best results, archives should be imported into new profiles.

    Export and Import Profile on the menu

    Saving the archive file

    4. Deploying a Project

    See Using MyEclipse Application Servers for details on deploying projects. Below are some things to note about deployment that are specific to WebSphere.

    • A WebSphere server can be either running or stopped when projects are added unless the WebSphere deployment mode is set to In-Workspace, which requires the server to be running. See Deployment Modes for more information.
    • When using the In-Workspace mode, exploded and packaged deployment options are unavailable.
    • The Add/Remove tool deploys your project into WebSphere automatically with no need to load the administrative console. Additionally, WebSphere logs the deployment process to the Console view if you want to examine it.

      To view the deployment log, click the drop-down arrow  on the Servers view toolbar, and select Websphere Deployment.

        The important line of the log to notice is the last line stating: Application <Your application name> installed successfully.

          Application deployment log in the Console view