Automatically Exporting a Plug-in Project as a Bundle

The Red App Bundle wizard creates a Red App bundle executable JAR file automatically. This wizard does the following:

Creates the bundle.properties and bundle.crt files
Signs all JARs in your bundle with your digital certificate
Generates the bundle ZIP file as a ZIP archive
Performs basic validation of a Red App to catch common errors before you submit your Red App bundle to Sabre. For more information, see the Red App Bundle Wizard description.

To use Red App wizards, you must install the Red App development tools software. For installation procedures, see How Do I Start?.

Important

If your project is a Sabre Scribe scripts plug-in, do not use this procedure. Instead, complete automatically Exporting a Sabre Scribe Project as a Bundle.

Important

In case of any issues with exporting your bundle it’s recommended for you check that Eclipse is using JDK, not JRE.

Before you begin:

Review Preparing to Create and Upload a Red App Bundle. This includes creating a redapp.xml file.
Add your digital certificate to your local key store. If you do not have a key store, create it.

You should use a key store in place of your digital certificate. When you run this wizard, the key store will be requested. The key store contains the digital certificate that is used to sign the JAR files. The wizard automatically exports this exact same certificate to your Red App package.

For more information, visit the following: http://docs.oracle.com/javase/8/docs/technotes/tools/windows/keytool.html

From the Eclipse workbench menu bar, choose File > Export.
In the Export dialog, expand Red App Development, then choose Red App Bundle. Finally, click Next.
Select all the plug-ins and fragments in your plug-in project. This includes your main Red App plug-in and any plug-in dependencies.
On the Destination tab, choose the destination folder for your Red App bundle.
On the JAR Signing tab, provide the required information.
- Signing jar with a keystore stored in file, requires filling the fields below:
  - Keystore location
  - Keypass
  - Alias
  - Storepass
- Signing jar with a certificate installed on a hardware token, requires filling the fields below:
  - Keystore location (has to be set to NONE to unlock disabled input fields)
  - Alias
  - Storepass
  - Storetype
  - Provider Class
  - Provider Arg
    
    Example of eToken.cfg file:
    
    name=eToken library=c:\WINDOWS\system32\eTPKCS11.dll
    
    Please note that the content of said file may differ depending on your token provider. If you are unsure how to configure said file please see your token provider’s documentation or contact their support.
Click Next .
Select your main Red App plug-in from the list.
When you are done, click Finish.
After your bundle is created, verify your bundle against the bundle requirements.

Next, upload your bundle and test your Red App.