Deployment Status
Deployment Status includes Deployment Log, Deployed Processes, Deployed Services, Partner Definitions, and Resource Catalog.
Deployment Log
The deployment log shows messages that are generated when new and modified business process archive (.bpr) files are added to the ActiveBPEL_Tomcat\bpr folder. Messages include successful deployments, loading or replacing of WSDL files, errors and warnings.
Each time you start the ActiveBPEL Administration Console, a new deployment log is created. Deployment logs are not saved.
Deployed Processes
The Deployed Processes page lists all business process files that have been deployed into the ActiveBPEL_Tomcat\bpr folder.
Select a process to view details. To view running, faulted, or complete processes, see Process ID and Process Details.
Deployed Process Detail
The Deployed Process Detail page shows the deployment descriptor (.pdd) and process (.bpel) XML source code that have been deployed to the ActiveBPEL engine in a business process archive (.bpr) file.
Select View Process Graph to see the process in Outline view and Graph view. For details on using these views, see Process ID and Process Details.
Partner Definitions
A partner definition file contains the service information
for a partner link that has been deployed designated as a principal endpoint
reference in the process deployment descriptor (.pdd) file. For
details, see the docs
folder of the ActiveBPEL
engine installation or see the ActiveBPEL Designer Online
Help.
If any principals have been defined, you can select one to view details.
Deployed Services
A deployed process contains at least one My Role partner link, and this partner link is assigned a service name in the Process Deployment Descriptor (PDD) file. The service name identifies the WSDL that the ActiveBPEL engine generates during deployment, and adds to the Services page. The WSDL includes the messages, operations, service, and binding details for the Web Service exposed by the process’ My Role partner link.
The process receives messages at the Web Service address, which is shown in the following example:
http://localhost:8080/active-bpel/services/[servicename]?wsdl
Note: Some services are deployed as external, indicating they are not exposed as Web Services. An example is a Retry Policy service, which is a process deployed to tell the engine how many times to retry a non-communicating service. This type of process is not intended for outside consumption. External services are listed, but are not linked, on the Deployed Services page.
The following details and links are included on the Deployed Services page.
Name |
Service name assigned to a My Role partner link in the PDD file. Select the name to link to the WSDL generated for this partner link. The WSDL is the Web Service that receives inbound messages. The Web Service address is in the form of: http://localhost:8080/active-bpel/services/[servicename]?wsdl |
Process Name |
Process containing the My Role partner link associated with this service |
Binding |
Standard SOAP binding styles indicating how to format inbound messages for the service. Can be one of:
|
Partner Link |
Name assigned to a My Role partner link that is exposing the service. Select the name to link to the Deployed Process Version Detail page. |
Partner Definition Details
The following details are displayed for the selected principal.
Partner link type |
The partner link type used in the partner definition for the principal |
Role |
Role defined for the partner link type |
Select a partner link type to view the namespace and endpoint reference details for the partner definition.
Resource Catalog
The Resource Catalog is the centralized cross reference for all WSDL, schema and other resource files referenced in the .pdd files deployed to the ActiveBPEL engine.
Any resource in the catalog can be accessed by any deployed BPEL process and only one copy is maintained. There are no restrictions based on the deployment context.
Item |
Description |
---|---|
Total Reads |
The number of reads to retrieve resource file information during process execution (in cache or not) |
Disk Reads (%) |
The number of reads made to resource files not in the cache expressed as an absolute number and percentage of Total Reads |
Cache Size |
The number of resource files in stored cache. The default is 100. You can set cache size on the Configuration page. Modifying the cache size may improve engine performance See the Engine topic. |
The Deployed Resources list shows the type and namespace for the resources.
You can do the following from this page:
- Select a resource to view details.
- Select one or more options from the Selection Filter option list to view a selection of resources. Narrow the list of displayed resources by selecting a resource type (such as WSDL, XSD, or XSL), a resource name, and/or a target namespace.
Resource Detail Page
The Resource Detail page shows the same information that is on the Resource Catalog for each resource and also displays the XML source code.
Type |
The resource type, such as WSDL or XSD |
Location |
The actual physical location where the resource is loaded from. This helps to uniquely define the location when the BPR was created and can be used to have multiple resource files of the same name deployed to the engine. The resource location is referenced in the .pdd file |
Namespace |
Target namespace in the resource |
Back to ActiveBPEL® Engine Administration Console Help
Copyright (c) 2004-2008 Active Endpoints, Inc.