Default distribution of WSO2 Business Process Server comes with embedded H2 database as BPEL engine's persistence storage and other settings which are suitable for use in development environment. But when you are going to production with WSO2 Business Process Server, there are several configurations you need to change according to your production requirements. These configurations will change based on how much requests BPS is going to handle per second, your auditing and monitoring requirements, performance requirements and nature of your process. Following are the main things you should do before going production with WSO2 BPS.
Those deployment issues are displayed under the relevant package in "Package Dashboard" page.
<wsdl:service name="HelloService123"> <wsdl:port name="HelloPort" binding="tns:HelloSoapBinding"> <soap:address location="http://az:9763/services/helloWorld"/> </wsdl:port> <port name="LoanServicePort" binding="tns:HelloSoapBinding"> <soap:address location="https://gb:9443/services/LoanService"/> </port> </wsdl:service>
<wsdl:service name="HelloService123"> <!--<wsdl:port name="HelloPort" binding="tns:HelloSoapBinding"> <soap:address location="http://az:9763/services/helloWorld"/> </wsdl:port>--> <port name="LoanServicePort" binding="tns:HelloSoapBinding"> <soap:address location="https://gb:9443/services/LoanService"/> </port> </wsdl:service>
Note 1:
Above mention configuration optimizations are true for Apache ODE also.
Note 2: Above mention best practices are valid for WSO2 Business Process Server 3.1.0 and upward. You can do the above optimizations to older versions WSO2 Business Process Server, but configurations and configuration mechanisms will be different. All of the above optimizations are supported by Apache ODE, but configuration is very different from WSO2 Business Process Server.
When it comes to BPEL development in WSO2 BPS, BPEL developer need to aware some scenarios which could lead to some problems. Those are listed as follows.