Testing MBO Package Deployment to a Test Domain

Sybase recommends that enterprise deployments always use a separate domain strictly used for development testing. Testing allows platform administrators to validate runtime and package deployment properties in the test domain, and then fine-tune properties as required for a production deployment environment. MBO packages are the most common deployment package and will be used to demonstrate this taskflow. However all packages types should be tested.

1. Enabling a Multitenancy Environment with Domains
   Platform administrators can add new domains to the Unwired Platform environment to facilitate tenants' administration of their own components.
2. Deploying and Managing MBO Packages
   Use Sybase Control Center to deploy MBO packages created by developers to a production Unwired Server and manage package configuration. When an administrator deploys a package to a production server, they are responsible for updating package properties to use production values to replace the development or test values assigned by developers.
3. Tuning Package Properties to Reduce EIS Load
   Deploy the package to a test domain and use a test application to determine what refinements can be made to reduce EIS load for a production environment.
4. Tuning Connection Pool Sizes
   Platform administrators can tune the maximum pool size to data source connections for improved performance. This ensure that adequate EIS resources are allocated for servicing the Unwired Platform runtime.
5. Importing Tested Package Archives to a Production Server and Domain
   Once tested, the exported package archive can be imported to a production domain on a production Unwired Server. Importing the archive deploys the packages it contains to a different server so no subsequent configuration is required. The values configured previous to the export process is reused in the new environment.