Problem: Deployed Package does not work as expected.
An unsuccessful refresh of connection profile properties can cause a deployed package to not operate as expected.
Connection profile properties can be modified after developing a service bound to an endpoint associated with the connection profile. At the time the services package is created, packager attempts to refresh connection properties while generating the meta-data within ear files for packages containing such services. For the refresh to succeed, certain connection profile types and transports that can be used as endpoints, such as JMS, require that the server identified by the profile be accessible.
If the server is unavailable, as is the case when the server is down or the when the server subnet is not reachable, the packager uses the original connection properties and issues a warning message identifying the problem.
Solution: Verify that the server identified by the connection profile is accessible, return to the Services Package Profile to verify the properties, then create the services package again.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com