Configure assisted life-cycle WebSphere Application Server Community Edition servers

After you manually create a middleware server representation of a WAS Community Edition server in the administrative console, you must update a few configuration settings so that they are defined specifically for the WAS Community Edition installation. If the middleware discovery function is enabled, we do not need to perform these steps.

Before you perform this task, consider the other options for configuring the WAS Community Edition servers:

If middleware discovery is disabled, perform the manual steps in this task to create a representation of the WAS Community Edition in the Intelligent Management cell. As a prerequisite, federate the node running the WAS Community Edition server and create a representation of the server in the administrative console.

Perform this task only if you have an existing WebSphere Application Server Community Edition environment and we do not want to enable middleware discovery to automatically create a representation of the environment.

  1. Update the WebSphere variables so that they match the settings on the node running the WAS Community Edition server. In the administrative console, click Environment > WebSphere variables.

    Edit the WASCE_HOME variable, which specifies the home directory of the WAS Community Edition installation. Default values are set at the cell scope level:

    • C:\IBM\WebSphere\AppServerCommunityEdition

    • /opt/IBM/WebSphere/AppServerCommunityEdition

    If the home directory is different on different nodes in our configuration, select the node scope and create the WASCE_HOME variable for the specific node.

  2. Update server operations for the WAS Community Edition server to include the user name and password.

    1. In the administrative console, click Servers > Server types > WebSphere Application Server Community Edition servers > wasce_server > Server operations.

    2. Edit the start and stop server operations to include the user name and password required to run these commands.


Results

We created a representation of the WAS Community Edition server in the administrative console. To view all of the WAS Community Edition servers, click Servers > Server types > WebSphere Application Server Community Edition servers.

The list of servers that displays on this administrative console page includes all of your complete life-cycle, assisted life-cycle, and discovered WebSphere Application Server Community Edition servers. If we have WebSphere Application Server Community Edition dynamic clusters defined, the cluster members are also listed on this administrative console page.


What to do next


Related concepts

  • WebSphere Application Server Community Edition servers


    Related tasks

  • Add assisted lifecycle middleware servers
  • Configure middleware server operations
  • Create complete life-cycle WebSphere Application Server Community Edition servers and dynamic clusters
  • Add, managing, and removing nodes
  • Add middleware servers to configurations
  • Create middleware server templates
  • Configure the external log viewing service
  • Create dynamic clusters
  • Create, editing, and deleting WebSphere variables

  • addNode command
  • Intelligent Management: middleware server creation administrative tasks
  • Intelligent Management: middleware server management administrative tasks