Preparing the rebranded Google Android application for distribution
As the BMC Digital Workplace administrator you can distribute your rebranded BMC Digital Workplace application as follows:
Install your rebranded BMC Digital Workplace application on mobile devices.
Publish your rebranded BMC Digital Workplace application to Google Play Store.
Due to a Google limitation, only BMC Digital Workplace 18.08 and later can be published to the Google Play Store.
For the purpose of Google Play Store publishing, you can change the mobile application package parameters. This change enables companies to publish the rebranded BMC Digital Workplace application to Google Play Store as their own application.
By using the Android Rebranding tool, you can rebrand the following application package parameters:
- Application name
- Package name
- Code version
For either of the distribution scenarios, you must prepare your rebranded application for distribution.
Before you begin
Download and install the Android SDK tool 24.0.3 or later.
To install the Android SDK tool
- Go to , and scroll down to the Command line tools only section.
- Download the appropriate file, depending on your operating system (Microsoft Windows or macOS).
- Extract the downloaded .zip file to any folder.
- Open the command line.
Navigate to cd PATH/tools/bin folder.
- Run the sdkmanager file by entering the following command:
- Install the build-tools package:
sdkmanager "build-tools;N", where N is the Android API Level (24.0.3 or later)
- Verify if the zipalign and the apksigner files are present in the following directory: PATH/build-tools/SOME_VERSION
To change the application package parameters
- Open the Android Rebranding tool.
- Select File > Open apk-file, and load your BMC Digital Workplace application.
- Click the Strings tab.
Enter new values in the following fields: Application name, Package name, Code version.
If any of the fields is not specified, you are not able to save the changes.
- Click Apply.
- Click the Pack apk-file button, and choose an appropriate directory to save your application with the changed package parameters.
To prepare the rebranded application for distribition
After you pack the rebranded BMC Digital Workplace application, you must sign it with a digital certificate. You can either use an existing certificate or generate a new one.
For more information about the signing process, see . For more information about the Android application signing tool, see .
To generate a digital certificate by using the keytool
The keytool is a certificate management utility that lets you administer your own public or private key pairs and associated certificates for use in self-authentication. For more information about the keytool, see .
- Open the command line, and run the following command:
keytool -genkey -v -keystore my-release-key.jks
-keyalg RSA -keysize 2048 -validity 20000 -alias my-alias
The keytool is located in the bin/ directory in your Java Development Kit (JDK). To see your JDK from Android Studio, select File > Project Structure, and then click SDK Location.
- Provide passwords for the keystore and the key.
Provide Distinguished Name fields for your key.
The keystore is generated as the my-release-key.jks file, and is saved to the current directory.
The keystore contains a single key that is valid for 20,000 days.
To sign the application
- Open the command line.
- Navigate to the cd PATH/build-tools/SOME_VERSION folder.
- Run the zipalign file:
zipalign -p 4 PATH/dwp_rebranded.apk PATH/dwp_rebranded_aligned.apk
- Run the apksigner file:
apksigner sign --ks PATH/keystore_key.jks PATH/dwp_rebranded_aligned.apk
- Run the signing verification:
apksigner verify PATH/dwp_rebranded_aligned.apk
After the preparation procedures are done, you can distribute the rebranded BMC Digital Workplace application by using either of the following possibilities:
- Install your rebranded BMC Digital Workplace application on mobile devices.
- Create an application in Google Play Store, and publish your rebranded BMC Digital Workplace application with the changed package parameters as your company's own application.
For more information about Google publishing, see the official .