Deploying an MBO Package with the Deploy Wizard

Use the Deploy wizard to deploy an existing MBO package or to create an MBO package from a deployment unit file.

Prerequisites

If your developers have created a custom filter for the mobile business object you are deploying, you must copy class files to the primary server before you deploy the package that uses those filters. If you copy the filters to a secondary server by mistake, they are deleted when you deploy the package to the primary server.

To locate the name of the primary server, look at the server list in SAP Control Center. Servers are listed according to their cluster role (that is, primary or secondary servers). SAP Control Center automatically identifies the primary server and lists it first, followed by secondary servers.

Task

Because the deployment unit file contains package name and other information, you do not need to select a package from the list of available packages; SAP Mobile Server creates the package automatically according to what has been defined in the deployment file.

Note: If the connection properties of an MBO or operation use credentials that have been customized manually by a developer, the back-end data sources connection properties of these MBOs and operations cannot be updated by an administrator when using the Deploy Wizard.

Instead, the administrator can update these properties after the MBO or operation is deployed to an SAP Mobile Server. When the server connection is created on SAP Mobile Server, the administrator can then change connection properties in SAP Control Center by clicking on the Connections node in the left navigation pane.

In the left navigation pane, expand the Domains folder.
Choose a domain name, then select Packages.
In the right administration pane, click the General tab.
Click Deploy.
Follow the instructions in the wizard to configure a package so it can be deployed.

Configuring Deployment Properties
Set the properties for packages being deployed on SAP Mobile Server.
Mapping Roles for a Package
SAP Mobile Platform uses a role mapper to map logical and physical roles during an access control check. This allows developers to create applications that incorporate a logical access control policy. When the application is deployed, a security administrator can work with the developer to understand what the logical roles in the application were intended to do and map these logical roles to physical roles that exist in the real security system. Role mappings performed at the package level override the mappings set at the global level. Package-level role mappings apply to all packages that use the same security configuration, even if the package is deployed in multiple domains. You can set the mapping state either when managing roles, or after package deployment.
Updating Server Connection Properties
Configure the production version of server connection properties. Typically, the endpoint and role mapping a developer would use are not the same for a production system. Administrators must reset these properties accordingly.
Reviewing the Deployment Summary
Review the properties you have supplied before deploying the package to SAP Mobile Server. This allows you to change errors before making the deployment units available via the package created for that purpose.

Parent topic: Deploying MBO Packages