Working with activity implementations

Activity implementations define general properties of a technology (for example, queue manager name for WebSphere MQ or broker for WebSphere Message Broker). Using associations on the Models tab, connects the model to the technology.
Some property values that activity implementations need include:

  • Operating system
  • Host name
  • Type of extension or instrumented application
  • Technology details.

Deployed configurations are organized by profile, transaction pathway, and activity implementation. This does not restrict another activity implementation from the same or different profiles and transaction pathway from using the same technology.

This section includes:

Was this page helpful? Yes No Submitting... Thank you