On the application list page, click the application name. For example, click the application mPaaS Demo created in the previous step. See the following steps:
- The app name appears at the top left, where you can switch apps.
- The right side of the page displays a list of component services provided by mPaaS.
On the Application details page, click to open the Configure application page.
On the Configure application page, click to open the Code configuration page.
On the Code configuration page, enter Package Name, namely com.mpaas.demo, such as com.mpaas.demo. Then upload the compilation, and add the signed APK install pack. For the information about the APK after quickly generating the signature, see Generate the signature APK for the console.
On the Code configuration page, fill in the information, then click Download Configuration to get the configuration file of mPaaS.
The configuration file is a compressed package file. This compressed package includes a
.config file and a
yw_1222.jpg encrypted picture.
- If you are a public cloud user, you need to ensure the value of
.configfile is not empty. You can ignore the
yw_1222.jpgfile, because the public cloud environment has abandoned this file.
- If you are a Apsara Stack user, you do not need to focus on the value of
base64Code. See Generate encrypted pictures (Apsara Stack configuration files). Generate the encrypted pictures of Apsara Stack manually, then replace the
yw_1222.jpgfile downloaded from the console.
Based on the native AAR method, this documents introduces the process of importing configuration files to the project.
- If you are using the mPaaS Inside method, see mPaaS Inside access process.
- If you are using the component-based access (Portal&Bundle), see The introduction of componentization access process.
- Open the existing project in Android Studio, click mPaaS > native AAR access.
- In the access pane, click Start Importing under the importing App configuration.
Select I downloaded the configuration file Ant-mPaaS-xxxx.config from the console, which is ready for importing to the project, then click Next.
In the window of Import mPaaS configuration files, select the App Module to be imported and the configuration file, then click Finish.
- After the process finishes, you will receive a prompt message that the configuration file has been imported successfully. Till now, you have completed the process of importing configuration files manually.
Besides, the mPaaS plug-in also supports the automatic pulling method to add configuration files. As mentioned in the preceding paragraph, when you import manually, you need to download configuration files from the console. Then add the files to the project manually through the mPaaS plug-in. For the automatic pulling method, you can log on to the mPaaS plug-in by using the Access Key information of your account. The mPaaS plug-in can pull configuration files from the console automatically, then add the files to the project. For more details, see Pull configuration files automatically。