Actions for the BMC Middleware Automation integration

Using default actions

This topic provides a list of default actions that you can use to perform various functions in BMC Middleware Automation. To learn more about Action Packs, see Action-packs and Creating-and-using-actions.

Before you begin

If you want to deploy BMC Middleware Automation actions through BMC Release Lifecycle Management suite products, you need to define certain Server Profile properties. You can set these properties in either the channels or channel templates in the BMC VaraLogix Q Deployment Automation interface. For more information, see Defining-properties-for-deploying-BMC-Middleware-Automation-actions.

BMC Middleware Automation IBM WebSphere Actions

The following table shows the out of the box actions for BMC Middleware Automation when connecting to WebSphere 6.1/7.x.

Action Name	Description	Required Properties
bma@websphere_jdbc_install	Creates a JDBC Resource on the defined scope	JDBCProvider_Name - Name of the JDBC Provider to add target_scope - Scope of the target (Cell, Node, Cluster, <serverName> DataSource_Name - Name of the datasource bma_version token
bma@websphere_jms_queue_install	Creates a JMS queue on the defined scope	queue_jndi_name - JNDI name of the queue queue_name - Queue Name target_scope - Scope of the target (Cell, Node, Cluster, <serverName> bma_version token
bma@websphere_jms_topic_install	Creates a JMS Topic on the defined scope	topicspace_name - topic Space Name topic_name - Topic Name topic_busname - Bus Name topic_jndi_name - JNDI name of the Topic target_scope - Scope of the target (Cell, Node, Cluster, <serverName> bma_version token
bma@websphere_jvm_heapsize_install	Changes the heap size value on a server	server_name - Server to change the heap on maxHeapSize - Value to set the Heap bma_version token
bma@websphere_server_install	Create a server on a node in the node list	server_name - Server name to create bma_version token
bma@websphere_servercluster_install	Create a cluster on a cell	cluster_name - cluster to create server_name - server to add to the cluster node_name - node where server resides bma_version token

BMC Middleware Automation Oracle WebLogic Actions

The following table shows the out of the box actions for BMC Middleware Automation when connecting to WebLogic 10.3/11g.

Action Name	Description	Required Properties
bma@weblogic_cluster_install	Installs a cluster in the Domain	adminserver_name - Admin Server name                                                                     domain_name - Domain for cluster name cluster_name - Cluster to create name server_name - Server to add to cluster name bma_version token
bma@weblogic_jdbc_install	Create a Jdbc resource	adminserver_name - Admin Server name domain_name - Domain name server_name - Server to add jdbc jdbcdatasource_name - Name of Jdbc to create bma_version token
bma@weblogic_jms_install	Create a JMS resource	adminserver_name - Admin Server name domain_name - Domain name server_name - Server to add jms jmsserver_name Name of JMS to create bma_version token
bma@weblogic_server_install	Create a server on the Domain	adminserver_name - Admin Server name domain_name - Domain name server_name - Server name to create bma_version token

Modifying existing actions

1. Click the Define tab.
2. In the Manage box on the left, click Actions.
3. On the Content tab, modify the existing action body.
4. Click Save or Save and Exit.

Creating new actions

1. Click the Define tab.
2. In the Manage box on the left, click Actions.
3. Click New Action after the list of existing packs.

4. Enter an appropriate label for the action. 

   Warning

   Note

   Name of BMA actions must start with the bma@ prefix.

5. From the Pack menu, select the pack to associate with the action.

6. From the Platform menu, select an appropriate platform for the action. 

   Warning

   Note

   When the system processes an action, "All platform" is the default if no platform-specific action is found.

7. Type or paste the content for the action. 

   Warning

   Note

   Properties are available to the script and can be tokenized in the script, using the following format: ${ph:<TOKEN VALUE>}

8. Click Save or Save and Exit.

If you were adding an action to a newly created pack, the new pack now appears at the bottom of the list of packs on the Actions list.

Creating single action for different applications/application servers

1. Click the Define tab.
2. In the Manage box on the left, click Actions.
3. Click New Action after the list of existing packs.
4. Enter the already existing for other application version action name.
5. From the Pack menu, select the pack to associate with the action.
6. From the Platform menu, select an appropriate platform for the action.
7. On the Reference tab, select the reference to the existing version of the application, for which the action was created.
8. Click Save or Save and Exit.