Preparing for Deployment
Preparing your BPEL process for deployment to the Process Server requires two tasks:
In addition, you may wish to read
Endpoint References and WS-Addressing Considerations before creating the process deployment descriptor file. This topic describes the details you may need for providing necessary deployment information.
If your partner's service requires authenticated access, see
Endpoint References Requiring Credentials for Access.
Preparing BPEL Files for Deployment
A BPEL file is ready for deployment to the Process Server when there are no errors in the Problems view and when a simulated execution of the process terminates normally.
To ensure your process is deployment-ready, complete this checklist:
- •Ensure that you have filled in all the required properties for each activity, such as partner link, operation and variable for receives (picks and event handlers), invokes, and replies.
- •Ensure that at least one receive or pick activity's Create Instance property is set to Yes.
- •Ensure that the Abstract Process property is set to No for the process.
- •Step through a simulated execution of the process, as described in Simulation and Debugging.
Selecting a Server Platform for Deployed Processes
Your BPEL process can run on any BPEL server. However, to deploy it to A Process Server, make a package of files (
.bpel,
.wsdl,.pdd) for deployment as described in
Creating and Deploying a Business Process Archive Contribution.
Process Developer includes the Process Server in your installation folder. You can deploy processes to this development server as you design and test processes. Instructions for deploying to this server are included in
Creating and Deploying a Business Process Archive Contribution.