There are common package management activities used by all package types: replication, messaging, unified, DOE-C, or ODATA.
These activities include:
Importing Package Contents
Import package contents after they have been exported from another Unwired Server.
Exporting Packages
Export a package to bundle one or more MBOs and package options in the selected package to create a new instance of a deployment archive. Typically, export is used to move the package contents onto another Unwired Server, however you can only import packages to the same domain as it was exported from.
Deleting a Package
Delete a package when you want to permanently remove all elements deployed on an Unwired Server. If you do not want to permanently prohibit access by removing these files, consider disabling the package instead.
Enabling and Disabling a Package
Enable or disable a package to allow or prohibit device access to the package. Disabled packages are still available to Sybase Control Center for Unwired Server. By default, all packages are enabled.
Configuring Synchronization Groups
Configure a synchronization group when a collection of MBOs must be synchronized at the same time. The synchronization group defines the logical unit of synchronization and data notifications required (depending on the payload protocol), as well as the synchronization frequency.
Configuring a Cache Group
Select and configure a cache group. The cache is part of the Unwired Server cache database (CDB) that is used to store data that is uploaded and downloaded from EIS servers and mobile clients during synchronization.
Configuring a Cache Group
Select and configure a cache group. The cache is part of the Unwired Server cache database (CDB) that is used to store data that is uploaded and downloaded from EIS servers and mobile clients during synchronization.
Mapping Roles
Configure role mapping to authorize client requests to access MBOs and operations. For each security configuration, platform and domain administrators can manage logical role mappings at the package level or at a domain level. Use the corresponding domain or package node in the left navigation pane to configure role mappings accordingly.
Configuring Synchronization Groups
Configure a synchronization group when a collection of MBOs must be synchronized at the same time. The synchronization group defines the logical unit of synchronization and data notifications required (depending on the payload protocol), as well as the synchronization frequency.
Configuring Package Subscriptions
Configure subscriptions and subscription templates to allow the device user to be notified when information is available, depending on the subscription properties configured for a package. Subscription templates allow you to configure predefined properties for a synchronization group. A client's first synchronization for a specified synchronization group results in subscription creation using both the template and client-specified properties.