Accessing Service Endpoints
When processes are deployed to Process Server, they are made available as service endpoints. Users and automated business processes start up process instances by submitting a request to a service endpoint.
In Process Console, you can see a list of services by selecting Service Definitions.
Default Service Endpoint: SOAP 1.1
By default, all services, except REST services, are listed at:
http://localhost:8080/active-bpel/services
This URL displays all services with a SOAP 1.1 binding. A request to start a SOAP 1.1 process can include:
- •Binding style of Document Literal, RPC Literal, RPC Encoded, or Policy Driven (handled by policy assertions)
- •Multiple-part message
- •Processes that may not be WS-I compliant
- •SOAP headers
- •Binding to HTTP GET and POST methods
Additional Service Endpoints
In addition to SOAP 1.1, you can use the following service endpoints:
- • http..active-bpel/services/SOAP12
SOAP 1.2 services. All services can be invoked except for REST services and the ActiveBpelAdmin service. Requests may be submitted to services exactly like SOAP 1.1 services, described above.
- • http..active-bpel/services/REST
Only REST services can be invoked. A request must be submitted with the following conditions:
- - Requests must conform to the input message defined in aeRest.xsd
- - HTTP methods HTTP GET, POST, PUT, and OPTIONS
- • http..active-bpel/services/XML
All services can be invoked except for REST and the ActiveBpelAdmin service. A request must be submitted with the following conditions:
- - Binding style must be document literal
- - Input and output messages must be a single-part element
- - Process must be WS-I compliant
- - Request is HTTP POST with header content-type of text/xml
- • http..active-bpel/services?JSON
All services can be invoked except for REST and the ActiveBpelAdmin service. A request must be submitted with the following conditions:
- - Binding style must be document literal
- - Input and output messages must be a single-part element
- - Input message must be represented in JSON
- - Process must be WS-I compliant
- - Request is HTTP POST with header content-type of application/json
- • http://host:port/active-bpel/catalog/project:/relative_path_to_resourceFolder
Examples:
http://localhost:8080/active-bpel/catalog/project:/AutoStep/wsdl/telco.wsdl
http://localhost:8080/active-bpel/catalog/project:/AutoStep/schema/telco.xsd