Integration with BladeLogic Server Automation

Integrations with the BladeLogic Server Automation product usually involve server and application management performed through the application adapter for BladeLogic Server Automation. The application adapter for BladeLogic Server Automation implements the provided web service tunneling API. The API exposes all the BladeLogic Server Automation actions available in the GUI.

When creating an integration with BladeLogic Server Automation, carefully consider the following application capabilities:

• BladeLogic Server Automation uses a CLI-type approach to integration. In this approach, each action is exposed as an independent command with its own independent memory and CPU resource requirements.
• BladeLogic Server Automation can manage thousands of servers and can execute approximately 128 concurrent commands against managed servers.
• Depending on the hosting platform, some of the BladeLogic Server Automation commands have execution times in hours.
• The application adapter for BladeLogic Server Automation can invoke NSH and Jython scripts as commands.

These capabilities can translate into:

• Large managed object count
• High transaction count
• High resource utilization
• Concurrent command execution

The application adapter for BladeLogic Server Automation can manage the resources consumed by the independent commands exposed by the BladeLogic Server Automation API. The adapter provides a configuration parameter that you can use to manage the Java Virtual Machine (JVM). This parameter, JVM Options, sets the JVM parameters and allocates memory. Using this parameter, you can control the amount of memory allocated for every init, connect, or execute command.

The application adapter for BladeLogic Server Automation is designed to handle concurrent execution threads. This capability enables the adapter to execute multiple concurrent BladeLogic Server Automation commands. The adapter can pool and share connections between commands that are executed using the same credentials. The adapter also has command time-to-live configuration parameters that can expand or reduce the time the adapter waits for a response to an executed command.