In development or testing environments, members of these teams can deploy directly to development instances of Unwired Server by using a supported deployment method. However, in production environments, development teams are typically restricted from performing these direct deployment activities; instead, the generally accepted practice is to package their deployment units in required format (for example, a .ZIP file for Hybrid App packages), then pass the deployment binary to the corresponding domain administrator for deployment.
| Method | System Life Cycle Stage | Volume | Restrictions |
|---|---|---|---|
| supadmin.bat | Automates the deployment to pre-production or production Unwired Servers. This utility is typically used within a custom-developed deployment script or for CTS. | Large | Typically not used by development teams, or for the deployment of isolated packages. |
| Deploy wizard in Sybase Control Center | Administrator managed to pre-production or production Unwired Servers. | Small or individual | None. |
| Package export and import from Sybase Control Center | Administrator-controlled bulk transfers between development and pre-production environment, since the data and Unwired Server or cluster configuration is not as sensitive to differences. See Transporting Packages Between Environments with Export and Import in Sybase Control Center for Sybase Unwired Platform | Medium to large | Transferring package between development and production environments, since the backend data and Unwired Server or cluster configuration are different. |
| Package transport with CTS | Transferring the complete set of deployed packages in SAP environments among pre-production and production servers. Relies on supadmin.bat to export packages to CTS. | Large | Non-SAP environments. |