esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...

Chapter 6: Adapting Imported Services to a Domain
Tuning BPEL Server Deployments
A Progress Sonic BPEL Server installation for deployment and its configurations in the
deployment domain adapt the BPEL services to their runtime environment.
Specifying Persistence
A Sonic BPEL Server installation can be set to persist its data in one of three ways:
● When you choose memory, be sure that adequate memory is available on the target
systems after allowing for the operating system, enterprise resources, and JVM
memory usage.
● When you choose embedded storage, specifying a storage directory will establish
the store locally on each system where the BPEL server runs. Be sure that there is
adequate disk space to accommodate the store. It is recommended that the data
storage directory is a different directory from the BPEL service staging directory so
that the staging directory can be easily deleted and recreated as needed.
● When you choose your other database, you can specify oracle or mysql:
■ For oracle, set the Oracle SID, the machine name, port, user name, and password.
■ For mysql, set the database name, host name, port, user name, and password.
Using a Callback URL
MyRole is the local endpoint for a partner link defined by the process. It is used by the
BPEL Server in the following two cases:
● ReplyTo / Fault To for outbound invocations when asynchronous transport is used.
● Explicit assignment from a myRole of a partner link. The value is determined using the
service configured CallBack URL.
You must also create a corresponding HTTP Direct acceptor (on the broker’s
configuration) and a WebServices Protocol configuration so that messages sent to the
callbackURL are routed to the BPEL Service entry endpoint.
Monitoring Destinations for Processing Replies
To monitor processing replies:
● Two temporary queues are used, one for synchronous replies and one for
asynchronous replies. Operations that are bound to ESB use synchronous replies.
● The format of temporary queue names uses the pattern:
container_name.service_name.queue_name
134 Progress Sonic ESB Deployment Guide 8.5