This documentation is for WSO2 Enterprise Mobility Manager 2.2.0. View documentation for the latest release.
Creating the Android App Catalog Application - Enterprise Mobility Manager 2.2.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

The device owners can search for applications that are made available in the Organizations App store, and install them on the device. The functionality of the app catalog application is similar to the Android play store. 

In this section let's look at how to generate the APK file for the app catalog application and then publish it to the store via the App Publisher.

Generating the App Catalog APK file

Follow the steps given below to generate the APK file of the app catalog application that is required to create and publish the application:

Before you begin

Ensure that you have downloaded and installed the Android Studio bundle before starting the configurations.

  1. Get a GIT clone of product-emm and navigate to the <PRODUCT_EMM_SOURCE_HOME>/modules/mobile-agents/android/app-catalog directory.

    git clone

    <PRODUCT_EMM_SOURCE_HOME>/modules/mobile-agents/android/app-catalog will be referred to as <APP_CATALOG> in this document.

  2. Update the Android Software Development Kit with the following:

    • SDK Versions 23 and 16. 

    • Build Tools Version 22.0.1.

    • Install or update Android Support Library.

    • Install or update Google Play Services.

    • Install Google USB Driver, if you are on a Windows platform.

  3. By default, the Android agent communicates with the server through HTTP. For production, this needs to be changed to HTTPS, by configuring the following parameters in the Java class named, which is in the org.wso2.EMM.agent.utils package: SERVER_PORT and SERVER_PROTOCOL.

    For more information see below:

     Generating a BKS File

    The Android agent must have the CA certificate inside the application when configuring the Secure Sockets Layer (SSL). The CA certificate is stored in a BKS (bouncycastle) file. Follow the steps given below to create and generate a BKS file: 


    Step 1: Creating a BKS file

    If you configured EMM for iOS, you can skip this step and move to Step 2 by using the already generated and imported Certificate Authority (CA), Registration Authority (RA), and SSL certificate files.

    1. Navigate to the openssl.cnf file of the OpenSSL installation. 

    2. Make a copy of the  openssl.cnf  file, move it to another location, and configure the file to generate version 3 certificates as shown below:

      [ v3_req ] 
      # Extensions to add to a certificate request 
      keyUsage = Digital Signature, Key Encipherment 
      [ v3_ca ] 
      # Extensions for a typical CA 
      # PKIX recommendation. 
      # This is what PKIX recommends but some broken software chokes on critical 
      # extensions. 
      basicConstraints = critical,CA:true 
      # So we do this instead. 
      #basicConstraints = CA:true 
      # Key usage: this is typical for a CA certificate. However since it will 
      # prevent it being used as an test self-signed certificate it is best 
      # left out by default. 
      keyUsage = Digital Signature, Certificate Sign, CRL Sign
    3. In the location where you modified and saved the openssl.cnf file, run the following commands to generate a self-signed Certificate Authority (CA) certificate (version 3) and convert the certificate to the .pem format:

      1. openssl genrsa -out <CA PRIVATE KEY> 4096
        For example: openssl genrsa -out ca_private.key 4096
      2. openssl req -new -key <CA PRIVATE KEY> -out <CA CSR>
        For example: openssl req -new -key ca_private.key -out ca.csr
      3. openssl x509 -req -days <DAYS> -in <CA CSR> -signkey <CA PRIVATE KEY> -out <CA CRT> -extensions v3_ca -extfile <PATH-TO-MODIFIED-openssl.cnf-FILE>
        For example: openssl x509 -req -days 365 -in ca.csr -signkey ca_private.key -out ca.crt -extensions v3_ca -extfile ./openssl.cnf
      4. openssl rsa -in <CA PRIVATE KEY> -text > <CA PRIVATE PEM>
        For example:  openssl rsa -in ca_private.key -text > ca_private.pem
      5. openssl x509 -in <CA CRT> -out <CA CERT PEM>
        For example: openssl x509 -in ca.crt -out ca_cert.pem
    4. In the same location, run the following commands to generate a Registration Authority (RA) certificate (version 3), sign it with the CA, and convert the certificate to the .pem  format. 

      1. openssl genrsa -out <RA PRIVATE KEY> 4096
        For example:  openssl genrsa -out ra_private.key 4096

      2. openssl req -new -key <RA PRIVATE KEY> -out <RA CSR>
        For example: openssl req -new -key ra_private.key -out ra.csr
      3. openssl x509 -req -days <DAYS> -in <RA CSR> -CA <CA CRT> -CAkey <CA PRIVATE KEY> -set_serial <SERIAL NO> -out <RA CRT> -extensions v3_req -extfile <PATH-TO-MODIFIED- openssl.cnf-FILE >
        For example: openssl x509 -req -days 365 -in ra.csr -CA ca.crt -CAkey ca_private.key -set_serial 02 -out ra.crt -extensions v3_req -extfile ./openssl.cnf
      4. openssl rsa -in <CA PRIVATE KEY> -text > <RA PRIVATE PEM>
        For example: openssl rsa -in ra_private.key -text > ra_private.pem
      5. openssl x509 -in <RA CRT> -out <RA CERT PEM>
        For example: openssl x509 -in ra.crt -out ra_cert.pem
    5. Generate the SSL certificate (version 3) based on your domain/IP address:

      You must add your IP address/domain as the Common Name. Otherwise, provisioning will fail. 

      1. Generate an RSA key.
        openssl genrsa -out <RSA_key>.key 4096
        For example:
        openssl genrsa -out ia.key 4096
      2. Generate a CSR file.
        openssl req -new -key <RSA_key>.key -out <CSR>.csr
        For example:
        openssl req -new -key ia.key -out ia.csr
        Enter your server IP address/domain name (e.g., as the Common Name else provisioning will fail.
      3. Generate the SSL certificate.
        openssl x509 -req -days 730 -in <CSR>.csr -CA ca_cert.pem -CAkey ca_private.pem -set_serial <serial number> -out ia.crt
        For example: 
        openssl x509 -req -days 730 -in ia.csr -CA ca_cert.pem -CAkey ca_private.pem -set_serial 044324343 -out ia.crt
    6. Export the SSL, CA, and RA files as PKCS12 files with an alias.

      1. Export the SSL file as a PKCS12 file with "wso2carbon" as the alias. 
        openssl pkcs12 -export -out <KEYSTORE>.p12 -inkey <RSA_key>.key -in ia.crt -CAfile ca_cert.pem -name "<alias>"
        For example:
        openssl pkcs12 -export -out KEYSTORE.p12 -inkey ia.key -in ia.crt -CAfile ca_cert.pem -name "wso2carbon"

      2. Export the CA file as a PKCS12 file with an alias.
        openssl pkcs12 -export -out <CA>.p12 -inkey <CA private key>.pem -in <CA Cert>.pem -name "<alias>"
        For example:
        openssl pkcs12 -export -out ca.p12 -inkey ca_private.pem -in ca_cert.pem -name "cacert"
        In the above example, cacert has been used as the CA alias. 
      3. Export the RA file as a PKCS12 file with an alias.
        openssl pkcs12 -export -out <RA>.p12 -inkey <RA private key>.pem -in <RA Cert>.pem -chain -CAfile <CA cert>.pem -name "<alias>"
        For example:
        openssl pkcs12 -export -out ra.p12 -inkey ra_private.pem -in ra_cert.pem -chain -CAfile ca_cert.pem -name "racert"
        In the above example, racert has been used as the RA alias. 
    7. Copy the three P12 files to the <EMM_HOME>/repository/resources/security directory.
    8. Import the generated P12 files as follows:
      1. Import the generated <KEYSTORE>.p12 file into the wso2carbon.jks and client-truststore.jks in the <EMM_HOME>/repository/resources/security directory.
        keytool -importkeystore -srckeystore <KEYSTORE>.p12 -srcstoretype PKCS12 -destkeystore <wso2carbon.jks/client-truststore.jks>

        When prompted, enter the keystore password and keystore key password as wso2carbon.

        For example:
        keytool -importkeystore -srckeystore KEYSTORE.p12 -srcstoretype PKCS12 -destkeystore wso2carbon.jks
        keytool -importkeystore -srckeystore KEYSTORE.p12 -srcstoretype PKCS12 -destkeystore client-truststore.jks

      2. Import the generated <CA>.p12 and <RA>.p12 files into the wso2certs.jks file, which is in the <EMM_HOME>/repository/resources/security directory.
        keytool -importkeystore -srckeystore <CA/RA>.p12 -srcstoretype PKCS12 -destkeystore wso2emm.jks

        For example:
        keytool -importkeystore -srckeystore ca.p12 -srcstoretype PKCS12 -destkeystore wso2certs.jks 
        Enter the keystore password as wso2carbon and keystore key password as cacert.

        keytool -importkeystore -srckeystore ra.p12 -srcstoretype PKCS12 -destkeystore wso2certs.jks 
        Enter the keystore password as  wso2carbon  and keystore key password as racert.


        Why does the following error occur: " keytool error: Invalid keystore format"?

        If you enter the wrong private key password when importing the <CA>.p12 or <RA>.p12 files, the wso2certs.jks file will get corrupted and the above error message will appear.

        In such a situation, delete the wso2certs.jks file and execute the following command to import the generated <CA>.p12 and <RA>.p12 files into the wso2certs.jks file again.
        keytool -importkeystore -srckeystore <CA/RA>.p12 -srcstoretype PKCS12 -destkeystore wso2certs.jks

        When the above command is executed, EMM will automatically create a new wso2certs.jks file with the imported file.

    Step 2: Generating a BKS file

    Follow all the steps given under step 1 before generating the BKS file to avoid errors.

    1. Generate the BKS file:

      Ensure that you have the bcprov-jdk16-1.46.jar file in the same folder where you will be generating the BKS file before you run this command.

      keytool -noprompt -import -v -trustcacerts -alias 'openssl x509 -inform PEM -subject_hash -noout -in ca_cert.pem' -file ca_cert.pem -keystore truststore.bks -storetype BKS -providerclass org.bouncycastle.jce.provider.BouncyCastleProvider -providerpath bcprov-jdk16-1.46.jar -storepass 'wso2carbon'

      If you are using an SSL certificate by a trusted authority such as GoDaddy, the cert.crt defined in the command should be the interim certificate. 

      keytool -noprompt -import -v -trustcacerts -alias godaddy -file cert.crt -keystore truststore.bks -storetype BKS -providerclass org.bouncycastle.jce.provider.BouncyCastleProvider -providerpath bcprov-jdk16-1.46.jar -storepass 'wso2carbon'
    2. Optionally, view the list of certificates in the BKS form using the following command:

      keytool -list -v -keystore "truststore.bks" -provider org.bouncycastle.jce.provider.BouncyCastleProvider -providerpath "bcprov-jdk16-1.46.jar" -storetype BKS -storepass "wso2carbon"
    3. Copy the generated truststore.bks file to the <EMM_SOURCE_HOME>/modules/mobile-agents/android/client/iDPProxy/src/main/res/raw directory and replace the original file. 
    4. Navigate to the <EMMM_SOURCE_HOME>/modules/mobile-agents/android/client/client/src/main/java/org/wso2/emm/agent/utils/ file, and configure the following:
      • Provide the HTTPS_HOST_IP as the value for the SERVER_PORT parameter.
        Example: 9443.
      • Change the SERVER_PROTOCOL to https://.
      • Provide the BKS file password as the value for the TRUSTSTORE_PASSWORD parameter.
      	public static boolean DEBUG_MODE_ENABLED = false;
      	public static boolean LOCAL_NOTIFICATIONS_ENABLED = true;
      	public static boolean GCM_ENABLED = false;
      	public static String SERVER_IP = "";
      	public static String SERVER_PORT = "9443";
      	public static String SERVER_PROTOCOL = "https://";
      	public static String API_VERSION = "1.0.0";
      	public static String SERVER_APP_ENDPOINT = "/EMM/api/";
      	public static String OAUTH_ENDPOINT = "/oauth2/token";
      	public static String SENDER_ID_ENDPOINT = "devices/sender_id/";
      	public static String IS_REGISTERED_ENDPOINT = "devices/isregistered/";
      	public static String LICENSE_ENDPOINT = "devices/license/";
      	public static String REGISTER_ENDPOINT = "devices/register/";
      	public static String UNREGISTER_ENDPOINT = "devices/unregister/";
      	public static String NOTIFICATION_ENDPOINT = "notifications/pendingOperations/";
      	public static String SERVER_URL = SERVER_PROTOCOL + SERVER_IP + ":"
      	public static final String TRUSTSTORE_PASSWORD = "<BKS_FILE_PASSWORD>";
      	public static final String EULA_TITLE = "POLICY AGREEMENT";
    5. Navigate to the <EMMM_SOURCE_HOME>/modules/mobile-agents/android/client/iDPProxy/src/main/java/org/wso2/emm/agent/proxy/utils/ file, and configure the SERVER_PROTOCOL as https://.

  4. Import the project on Android Studio, clean and build the project.

  5. Run the project on a device.

    The .apk file can be found in the <APP_CATALOG> directory.

Using the APK file you generated, let's get ready to create the app catalog application in the APP Publisher.

Create the App Catalog Application in the App Publisher

Follow the steps given below to create an application in the App publisher.

  1. Log in to the App Publisher using the following URL: https://<EMM_HOST>:<EMM_PORT>/publisher
  2. Click Add New Mobile Application that is under the Mobile Application drop down.
  3. Select Android for Platform on which the application (app) will be based on.
  4. Select the Store Type as Enterprise. The available store types are given below:
    • Enterprise - Refers to all apps that have been created by the organization.
    • Public - Refers to publicly available apps (e.g., free apps available online). 
  5. Select the APK file as shown below.

    The APK file size should not exceed 200MB.


  6. Click Next, and you will get the following screen:

    Enter the following details of the app.
    • Name - Enter the Name as Catalog application.
    • Display Name - Enter the Display Name as App Catalog Application. It is the name of the app that is displayed to the user.
    • Description -  A summarized description of the app.
    • Recent Changes - Optional. A summarized description of what is new in this app when compared to its previous version.
    • Version - Version of the public application. The version will be updated by default with the metadata of the APK file.
    • Category - The business category will be selected by default as the server reads this data from the APK file.
    • Visibility - Enter Internal/everyone. The app will be visible to anyone who accesses the store.
    • Tags - You can group mobile applications under a specific category using tags.  Define the category and press enter.
    • Click on the respective + buttons to upload the required images.
      • Banner - Image that will appear as the app banner.
      • Screenshots - Screenshots of the app so that the user can get an understanding of what the app offers. A maximum of four screenshots are allowed.
      • Icon file - The image that will be used as the application icon in the Store and when the application is installed on a device.

    The recommended image extension is .png while the recommended dimensions are as follows:

    • Icons: 124px x 124px
    • Screenshots: 288px x 512px (landscape) and 512px x 288px (portrait)
    • Banners: 705px x 344px
  7. Click Create. The created app will appear in the created list of apps.

Publishing the App Catalog Application

Device owners will not see this application in the App Store until it is published. Follow the steps given below to publish the application:

  1. Click Submit for Review for the App Catalog catalog application.

  2. Click Approve > Publish.
  • No labels