Problem: Modified datasource port information is not reflected during deployment of MBOs.
During the second deployment, the endpoint port is the original value 4100, and not 41007.
Solution: Run Ant scripts to modify datasource settings: Create an XML configuration file, and run configure.bat located in %SUP_HOME%\UnwiredPlatform\Servers\UnwiredServer\bin:
The port information is updated and reflected during deployment.
For each JDBC datasource, the database vendor's specific JDBC driver may expose its own connection properties. You can specify those properties in an XML configuration file by prefixing the property name with "jdbc:".
For example, the Sybase jConnect for JDBC driver for Sybase contains an IS_CLOSED_TEST connection property that you can set. This property can be a SQL query that jConnect sends to the database when the application calls Connection.isClosed(), or "select 1". If the query successfully executes, the connection remains open, and returns false. The jConnect driver also has an "INTERNAL" setting that enables jConnect to remember the state of the connection the last time it was used. Thus the database is not pinged with useless queries, especially in an appServer context where the isClosed() check is done each time a connection is checked into or out of a connection pool. To set the "INTERNAL" property from the Ant script, add:
<property name="jdbc:IS_CLOSED_TEST" value="INTERNAL"/>
See your JDBC driver documentation for information about driver specific connection properties.