Getting started with deploying Java EE applications

BMC BladeLogic Server Automation

8.1

BMC BladeLogic Server Automation Installation Guide

BMC BladeLogic Application Release Automation

8.1

BMC BladeLogic Application Release Automation Getting Started Guide

BMC BladeLogic Decision Support for Server Automation

8.1

BMC BladeLogic Decision Support for Server Automation Installation Checklist
BMC BladeLogic Decision Support for Server Automation Installation Guide for Oracle
BMC BladeLogic Decision Support for Server Automation Installation Guide for SQL Server

Step 1. Create a property class instance with specific property values for each managed Java EE application server.

For each WebSphere Deployment Manager (DMGR) or WebLogic domain that you want to manage, you must create an instance of a custom property class delivered with the product, and configure local values for your Java EE application server within the created instance.

For information about this task, see "Creating a property class instance and configuring application properties" in the BMC BladeLogic Application Release Automation Getting Started Guide.

Step 2. Associate the property class instance with the host server through a server property

After creating the property class instance for your WebSphere or WebLogic server, you must associate this instance with the target server by setting the name of the instance as the value of a server property.

For information about this task, see "Setting a Java EE Application property" in the BMC BladeLogic Application Release Automation Getting Started Guide.

Step 3. Distribute configuration objects to the target server

To enable the management of a target Java EE application server, you must distribute product-related configuration objects to the target server by running a Distribute Configuration Objects Job.

If the operating system on the target server is not supported by BMC BladeLogic Application Release Automation, set up a proxy server on a supported operating system and distribute the configuration objects to the proxy server.

For information about this task, see "Distributing configuration objects to the target server" in the BMC BladeLogic Application Release Automation Getting Started Guide.

Step 4.  Refresh data collection from the Java EE application server

After you run the Distribute Configuration Objects Job, you must perform an initial data refresh for the data obtained from the Java EE application servers.

Subsequent data refresh jobs are run automatically by BMC BladeLogic Application Release Automation, but you can control the scheduling of the data refresh or initiate data refresh on demand at any time.

At this point you are ready to browse your enterprise application through the Live node of the relevant servers. You can also test the connection to the Java EE application server while browsing it.

For information about this task, see "Controlling data refresh and refreshing on demand" in the BMC BladeLogic Application Release Automation Getting Started Guide.

Step 5. Customize component templates and import additional WebSphere templates

A group of out-of-the-box component templates are delivered to your BMC BladeLogic Server Automation Console by BMC BladeLogic Application Release Automation, with each template corresponding to a single component of a Java EE application server. In most cases, you will find these out-of-the-box templates sufficiently ready for the various operations that you plan to perform on your Java EE application servers. You may, however, still be interested in modifying and refining these component templates, especially if you want to add compliance rules to the templates and use them to analyze the compliance of your Java EE application servers with the defined rules.

For WebSphere application servers, only a select group of component templates are delivered to your BMC BladeLogic Console during installation, supporting only the major WebSphere assets. If you need additional component templates for other WebSphere assets, import them from the installation directories.

For information about this task, see "Out-of-the-box component templates" in the BMC BladeLogic Application Release Automation Getting Started Guide.