Configuration management

We saw in the earlier chapters that Enterprise Manager collects configuration snapshots that are useful in keeping track of the configuration changes. Enterprise Manager refreshes the configuration snapshot periodically, and any change in the configuration is also recorded in the repository. You can also use the configuration snapshots to compare the configuration of one target with another target of the same type.

Configuration data collected for BPEL PM includes:

• SOAP URL and SOAP callback URL

• Dehydration store details — host, port, s-id for dehydration store

• Cluster configuration if BPEL PM is part of cluster

• List of the BPEL domains and domain specific configuration parameters like minimum and maximum threads

• BPEL PM configuration files like collaxa-config.xml, jgroups-protocol.xml, and so on

• List of the BPEL processes deployed, and the artefacts for BPEL processes such as bpel.xml, xsds, wsdls, and so on

To see the latest collected configuration for a BPEL PM target...