Defining Package Properties in appConfig.js

Update the appConfig.js file in <SDK directory>/apps/packager with the desired package properties.

Context

Define the package properties in appConfig.js:

SAP Fiori applications and SAPUI5 reuse libraries to include in the package
Globally unique application identifier
Display names for the container app and the launchpad tiles
SAP Cloud Platform mobile service for SAP Fiori signing profiles to be used to sign the app
SAP Mobile Platform registration settings

Procedure

You must name your configuration file appConfig.js.

To make different groups of apps available to different user groups, create a separate appConfig.js file for each package.

Specify the appConfig.js properties.

You can specify the following properties:

Property	Description
`appID`	Application identifier for SAP Mobile Platform registration; must be defined if `"fioriURLIsSMP":true`. Note The hybrid application must be configured in SAP Mobile Platform before the app is launched on the client device.
`appName`	Identifies the SAP Fiori application name shown on the logon screen and on the device. The default value is "SAP Fiori Client".
`appVersion`	Version identifier.
`bundleId`	Globally unique application identifier. Select the bundle ID carefully to ensure that different applications do not overwrite each other, and to ensure that an updated application correctly replaces an existing application. Use reverse domain name service (reverse DNS) notation, for example, `com.acme.crm.app`. Note For iOS app signing to work correctly, the bundle ID you use in `appConfig.js` must match the app ID/bundle ID of the iOS provisioning profile (created in the Apple portal or Xcode) that created the corresponding iOS signing profile in SAP Mobile Secure.
`iOSSigningID` `androidSigningID`	SAP Cloud Platform mobile service for SAP Fiori signing profile IDs used to sign the application binary for iOS and Android. For more information, see the `signingids` command description (below).
`fioriURL`	Runtime endpoint for the application: If `"fioriURLIsSMP":true`, enter the URL of the SAP Mobile Platform server. If `"fioriURLIsSMP":false`, enter the URL of the SAP Fiori front-end server. The format is `<protocol>://<host>:<port>`.
`fioriURLIsSMP`	Defines whether the runtime endpoint is SAP Mobile Platform or the SAP Fiori front-end server. If `"fioriURLIsSMP":true`, the device registers with SAP Mobile Platform using the given `appID`.
`prepackaged`	Set to `true` to enable the boot logic to work correctly at runtime.
`offline`	Set to `true` to create offline OData stores. Offline apps require SAP Mobile Platform (`"fioriURLIsSMP":true`).
`singleApp`	Not currently supported.

The applications property array defines the applications and components to download.

If the application that you want to package does not have an application descriptor (also known as the application manifest file, manifest.json), you must specify the title, i18n, and icon properties. If the application has an application descriptor, then the packager obtains this information from the manifest file.

Note

Example of an applications property array for an application that does not have an app descriptor (manifest.json):

   "applications":[
      {
         "id":"hcm.emp.payslip",
         "intent":"RemunerationStatement-displayPayslip",
         "title":"{{DISPLAY_NAME}}",
         "i18n": "i18n/i18n.properties”,
         "icon": "sap-icon://travel-expense-report",
         "url":"/sap/bc/ui5_ui5/sap/hcm_ps_mon"
      }
   ]

The following table describes the subproperties of the applications property array:

Property	Description
`id`	Fiori component ID (required in all cases).
`intent`	Applications that have an `intent` property are mapped to tiles in the launchpad. The display name for the tile is derived from the `title` property, or from the application manifest file if no title is provided. Icons shown on the tile are derived from the application manifest file.
`title`	Display name for the app's launchpad tile. This overrides any title obtained from the application manifest file (if present). This property is required for applications that do not have a manifest file. If localized, use the locations tag. For example, `{{shellTitle}}`.
`url`	Location of the manifest file and resources files for the SAP Fiori application. See the example `appConfig.js` (below).
`scenario`	Indicates the component that provides the boot logic and offline store definitions for offline-enabled apps. When `"scenario":true`, the packager checks the application manifest file for the offline setup.
`reuse`	`"reuse":true` indicates that the component is a reuse component, such as a common library.
`i18n`	Path of the internationalization properties file, relative to the root of the application resource tree. For example, `i18n/i18n.properties`. This property is only required for applications that do not have a manifest file.
`icon`	Name of the icon (as defined in the SAP Icon pool). For example, `sap-icon://travel-expense-report`. This property is only required for applications that do not have a manifest file.

Example appConfig.js

{
   "appID":"com.acme.fiori.app",
   "appName":"CRM",
   "appVersion":"1.0",
   "bundleID":"com.acme.crm.app",
   "androidSigningID": "b72be503e22cacfaf671d0affe674b40",
   "iosSigningID": "1d253111d50ae538abab86063189b9a4",
   "fioriURL":"https://mo-a1c4fd27e.mo.sap.corp:8081",
   "fioriURLIsSMP":true,
   "prepackaged":true,
   "offline":true,
   "singleApp":"",
   "applications":[
      {
         "id":"cus.crm.mycontacts",
         "intent":"ContactPerson-MyContacts",
         "title":"My Contacts",
         "url":"/sap/bc/ui5_ui5/sap/crm_mycont"
      },
      {
         "id":"cus.crm.myaccounts",
         "intent":"Account-MyAccounts",
         "title":"My Accounts",
         "url":"/sap/bc/ui5_ui5/sap/crm_myaccounts"
      },
      {
         "id":"sap.cus.crm.lib.reuse",
         "url":"/sap/bc/ui5_ui5/sap/crm_lib_reuse/sap/cus/crm/lib/reuse",
         "reuse":true,
         "scenario":true
      }
   ]
}