SMP(MBO): Deploy options
In order to complement the official documentation about the SMP MBO Deploy procedure, i’m creating this Blog.
In here, let’s explore 2 options of deployment from the SDK project to the SMP MBO Server.
I’m gonna use my DEMO SDK Project:
First (and easiest one), if your SDK server can “reach” your SMP server, you could automatically deploy your project like this:
You should have a valid Mobile Server connection:
With this option, you will define the following steps before deploying to the server:
- Define the package name and version number;
- Define your Mobile Server connection, Domain and Auth Provider;
- Define the App. Id.
- Select the MBO’s;
- Map the local SDK connections (Rest, SOAP, JDBC or SAP) to the SMP Server connections;
- Save local deploy package file.
After that, your package will be deployed to the server and will be available (inside your Domain) on the packages folder:
Sap Control Center (SCC):
Second options(if you don’t have a connection from the SDK server to the SMP server), you could create the .JAR file and deploy manually in the SMP Server using the SCC.
In your project, select the option below:
After that, you will go through the same process described above (not the Mobile server connection item).
Select the options below on your new file (Full or Incremental, depending if it’s a new package or a existing one):
New .JAR file created:
With the .JAR file, you should go to the SCC domain/package screen, and Deploy:
Going through the step by step options, the package will be deployed.
So now you’re all set to deploy your project based on your current landscape ??.