SOA ESB best practices

There are so many things to consider when dealing with web services.

*.            Strictly must use correct namespace. Please refer WSDL file for correct namespaces.

*.            When testing, better use SoapUI tool. Some other tools will may invoke service correctly. But their request and response may not complete.

*.            If the service is RPC type service, may use soap11 tab in the endpoint declaration.

*.            If service has more than one method, and you are going to access it via oracle database, you should add property call <parameter name="disableOperationValidation">true</parameter>

*.            Before creating a proxy service or any service, you need to have clear correct endpoint url, best way to get the correct url is check in the bottom of WSDL file. Always ask for the correct wsdl url.

*.            Don’t use similar names for two services. Better use different names. (Ex: service1 , secondService)

*.            Before giving to development, you must test the created service using soapUI tool. Because there are some compatibility issues with some services created using different platforms.

*.            If a service is working fine but cannot access, first look in log file. There will be all errors regarding the service invoke. Then you can finalize the error and solve that error. But if you cannot see any error or any log regarding the service invoke in log file, may be ports closed due to policy expiration or something. So must have to telnet to the service hosted port from appropriate server.

*.            Don’t be hurry or get panic. If something wrong in any service. Calmly check all configurations in the service.