Modified Configuration Profile Changes Not Deployed

Explanation: In Sybase Unwired WorkSpace, an MBO package is created from a database connection profile (for example, "PurchaseOrderDB") with particular connection parameters (for example, host and part of example1:9999), and then deployed to the Unwired Server.

During deployment, you create a Server connection (for example, "PurchaseOrderDB") in the Server Connection Mapping window, which creates a file in the Unwired Server at C:\Sybase\UnwiredPlatform\Servers\UnwiredServer\Repository\Instance\com\sybase\djc\sql\DataSource\default_PurchaseOrderDB.properties with connection information to the database.

In Enterprise Explorer, you change the connection profile information for the connection profile "PurchaseOrderDB" (for example you change the host and port to example2:9999) and then try to redeploy the package to the Unwired Server. During deployment, when you select PurchaseOrderDB under Server connection in the Server Connection Mapping window, its connection properties are listed in the table, and still show the host and port, example1:9999.

This behavior occurs because the information is retrieved from Unwired Server, and does not consider the change from the Enterprise Explorer connection profile (example2:9999).

Solution 1:

1. Create a new "Server connection" during the deployment, and enter the new connection information.

2. Redeploy the MBO package from Sybase Unwired WorkSpace, using the newly created Unwired Server connection.

Solution 2:

1. In the Unwired Server installation directory, change to this folder:

   <UnwiredPlatform-InstallDir>\UnwiredPlatform\Servers\UnwiredServer\Repository\Instance\com\sybase\djc\sql\DataSource\

2. Open the .properties file and change the connection information.