For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.

Register an application to a production environment

When we register an application to a production server, you upload its application descriptor, define its license type, and optionally activate application authenticity.

Before you begin

• Verify that MobileFirst Server keystore is configured and is not the default keystore. Do not use a server in production with a default keystore. The MobileFirst Server keystore defines the identity of MobileFirst Server instances, and is used to digitally sign OAuth tokens and Direct Update packages. You must configure the server's keystore with a secret key before we use it in production. For more information, see Configure the MobileFirst Server keystore.
• Deploy the adapters used by the app. For more information, see Deploy or update an adapter to a production environment.
• Build the application for our target server. For more information, see Build an application for a test or production environment.

When we register an application with a production server, you upload its application descriptor, define its license type, and optionally activate application authenticity. You might also define your update strategy if an older version of your app is already deployed. Read the following procedure to learn about important steps, and about ways to automate them with the mfpadm program.

Procedure

1. If your MobileFirst Server is configured for token licensing, make sure that you have enough available tokens on the License Key Server. For more information, see Token license validation and Plan for the use of token licensing .

   Tip: We can set the token license type of your app before you register the first version of your app. For more information, see Set the application license information.

2. Transfer the application descriptor from a test server to the production server.

   This operation registers your application to the production server and upload its configuration. For more information about transferring an application descriptor, see Transfer server-side artifacts to a test or production server.

3. Set the application license information For more information, see Set the application license information.
4. Configure the application-authenticity security check. For more information about configuring the application-authenticity security check, see Configure the application-authenticity security check.

   Note: We need the application binary file to create the application-authenticity file. For more information, see Enabling the application-authenticity security check.

5. If your application uses push notification, upload the push notification certificates to the server. We can upload the push certificates for our application with MobileFirst Operations Console. The certificates are common to all versions of an application.

   Note: You might not be able to test the push notification for our app with production certificates before your app is published to the store.

6. Verify the following items before you publish the application to the store.
   1. Test any mobile application management feature that you plan to use, such as disabling remote applications or displaying of an administrator message. For more information, see Mobile-application management.
   2. In the case of an update, define the update strategy. For more information, see Update MobileFirst apps in production.

Parent topic: Deploy MobileFirst applications to test and production environments