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.

Multiple tasks are involved in package deployment and management. Package administration tasks vary depending on the type of package you deploy.

Subscriptions
Subscriptions are managed with MBO packages. However, they are closely associated nonetheless with the device user, because it is the pairing of a user profile and registered and activated device account give the user subscription privileges. Subscriptions define what subset of data the user wants to receive when they synchronize.
Deploying an MBO Package to a Domain
Deploy an MBO package to Unwired Server using Sybase Control Center. Packages are initially created by developers, but are deployed and maintained on a production Unwired Server by administrators.
Selecting a Security Configuration for a Package
Designate a security configuration for a package in Sybase Control Center. This is a required step during package deployment, but you can later change the security configuration.
Mapping Roles for a Package
Configure package role mapping to authorize client requests to access MBOs and operations. Domain administrators can use a role mappings table to manage logical roles at the package level.
Managing Package Users
A package user is automatically registered when the user is successfully authenticated by the security configuration mapped to the MBO package. This is the identity used by the application to synchronize with the MBO package. The same identity is also registered as application user for native replication or messaging applications.

Parent topic: MBO Package Management Overview

Related tasks

Tuning Messaging

Created November 3, 2011. To comment on this topic, go to: DocCommentXchange.