WSO2 SOA Enablement Server can be ported into any servlet engine (WebLogic, WebSphere, Tomcat, etc.). The Overview of the Porting WSO2 SOA Enablement Server section in the Installation and Porting Guide includes a table of servlet engines and links to the porting instructions in Guides for Application Servers. The Manual Porting chapter provides an overview of porting issues.

We support a number of JMS providers, which we use for sending SOAP messages over JMS. WSO2 SOA Enablement Server can also be run as an NT Service on appropriate operating systems.

Note that for the supported application servers, the J2eeIntegrate Tool creates a deployable application (.war or .ear) and gives porting instructions.

The Raw Level Processing chapter includes sections on servlet transport and JMS transport, used when WSO2 SOA Enablement Server has been ported into a remote HTTP engine.

Please note that when WSO2 SOA Enablement Server has been ported to a servlet, Web services can only be published using persistent deployment (please see Deployment Scenarios for Embedded or Ported WSO2 SOA Enablement Server).

	Important
	If you want to port WSO2 SOA Enablement Server and WSO2 SOA Enablement Server UDDI together to one application server, you must use the parameter --context in the makeWar.bat (.sh) for the UDDI distribution.