All Products
Search
Document Center

Quick start

Last Updated: Aug 24, 2021
Important: mPaaS discontinued maintenance of the 10.1.32 baseline, effective from June 28, 2020. Use 10.1.68 or 10.1.60 series baseline. For how to upgrade the baseline version, see mPaaS 10.1.68 upgrade guide or mPaaS 10.1.60 upgrade guide.

MCDP supports three access modes: native AAR mode, mPaaS Inside mode, and component-based (Portal&Bundle) mode.

Prerequisites

  • The version of the baseline you are using is 10.1.60-beta or higher. mPaaS fully supports MCDP from version 10.1.60-beta of the baseline. Before adding the SDK, make sure that the version of the baseline you are using is 10.1.60-beta or higher. The version information of the baseline can be obtained from the Current mPaaS SDK version information in the mPaaS > Baseline upgrade menu.
  • Before you access the component to in the native AAR mode, add mPaaS to your project first.
  • If you want to connect the component to the mPaaS based on the mPaaS Inside mode, you need to first complete the mPaaS Inside access procedure.
  • If you want to connect the component to the mPaaS based on components, you need to first complete the Component-based access procedure.

Add the UC SDK

Native AAR mode

You can use the Component management (AAR) feature to install the Mobile Content Delivery Platform (MCDP) component in your project. For more information, see ARR component management.

mPaaS Inside mode

Install the Mobile Content Delivery Platform (MCDP) component through the Component management feature in your project
For more information, see Manage component dependencies.

Component-based (Portal&Bundle) mode

In your Portal and Bundle projects, install the Mobile Content Delivery Platform (MCDP) component through the component management feature.
For more information, see Manage component dependencies.

mPaaS initialization

In the native AAR or mPaaS Inside mode, you must initialize the mPaaS.

  1. public class MyApplication extends Application {
  2. @Override
  3. protected void attachBaseContext(Context base) {
  4. super.attachBaseContext(base);
  5. // Initialize callback settings for mPaaS.
  6. QuinoxlessFramework.setup(this, new IInitCallback() {
  7. @Override
  8. public void onPostInit() {
  9. // This callback indicates that mPaaS has been initialized, and mPaaS-related calls can be made in this callback.
  10. }
  11. });
  12. }
  13. @Override
  14. public void onCreate() {
  15. super.onCreate();
  16. // Initialize mPaaS.
  17. QuinoxlessFramework.init();
  18. }
  19. }

Add configuration

By default starting from version 10.1.68.18, the MCDP component does not initialize booth pulling and activities when the process starts. You need to manually add the following configuration to the AndroidManifest file to enable automatic initialization:

  1. <meta-data android:name="com.mpaas.cdp.autoInit" android:value="true" />

After upgrading from a lower baseline version to version 10.1.68.18, you need to manually add configurations to the AndroidManifest file to ensure the normal operation of the corresponding functions.

Follow-up steps

After the SDK is added, you can preset booths or dynamically configure booths based on business needs.