[CONF] Apache Ode > ODE Jbi and Axis2 properties overview

[confluence]

ODE Jbi and Axis2 properties overview Page added by Rafał Rusin Introduction ode-axis2.properties and ode-jbi.properties are used for engine configuration. Common properties Here, ode-jbi prefix is used. However for axis2, you need to replace it into ode-axis2. # Database Mode ("INTERNAL", "EXTERNAL", "EMBEDDED") # What kind of database should ODE use? # * "EMBEDDED" - ODE will create its own embbeded database (Derby) # and connection pool (Minerva). # * "EXTERNAL" - ODE will use an app-server provided database and pool. # The "ode-jbi.db.ext.dataSource" property will need to # be set. # * "INTERNAL" - ODE will create its own connection pool for a user- # specified JDBC URL and driver. ode-jbi.db.mode=EMBEDDED # External Database [JNDI Name] # JNDI Name of the DataSource for the ODE database. This is only # used if the "ode-jbi.db.mode" property is set to "EXTERNAL" ode-jbi.db.ext.dataSource=java:comp/env/jdbc/ode # Embedded Database Name [String] # Name of the embedded Derby database. This is only used if the # "ode-jbi.db.mode" property is set to "EMBEDDED". #ode-jbi.db.emb.name=hibdb #ode-jbi.db.emb.name=jpadb # Internal Database Configuration #ode-jbi.db.int.jdbcurl=jdbc:mysql://localhost/ode?user=sa #ode-jbi.db.int.driver=com.mysql.jdbc.Driver # DAO Connection Factory class. # uncomment the following for hibernate. #ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl # BPEL Event Listener # Uncomment the following for a debug output of BPEL navigation events. #ode-jbi.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener #debugeventlistener.dumpToStdOut=on/off ode-axis2.properties To configure those properties, please put ode-axis2.properties file in webapps/ode/WEB-INF/conf directory. # Used to redirect traffic to localhost instead of routing again via load balancer in clustered environment ode-axis2.cluster.localRoute.targets=http://myloadbalancer.com:8080/ode/processes/ ode-axis2.cluster.localRoute.base=http://localhost:8888/ode/processes/ ode-jbi.properties For JBI distribution, those properties are zipped into Service Assembly. For SMX4 OSGi bundle distribution, those are in SMX4/etc/org.apache.ode.jbi.cfg file. # Process Identifier Namespace [QNAME] # Namespace for processes created using the JBI integration. # This will be the namespace of the process identifiers (PIDs) ode-jbi.pidNamespace=urn:ode-jbi # Allow Incomplete Deployment ("true","false") # Should incomplete deployments be allowed? An incomplete deployment # arises when a service unit contains multiple processes and not all # of the processes can be deployed. If incomplete deployments are # allowed (true), the service unit will report success if any of the # processes can be deployed. If not allowed (false), a failure in # one process will prevent all processes from being deployed. ode-jbi.allowIncompleteDeployment=false # Class name of the message mapper that should be used to convert message # between ODE / NMS. # org.apache.ode.jbi.msgmap.JbiWsdl11WrapperMapper - use JBI WSDL 1.1 "wrapped" # org.apache.ode.jbi.msgmap.ServiceMixMapper # org.apache.ode.jbi.msgmap.DocLitMapper ode-jbi.messageMapper=org.apache.ode.jbi.msgmap.ServiceMixMapper Change Notification Preferences View Online