29.7.3. Publishing a mobile application on a web server

<< Prev   Next >>

29.7.3.1. General information

For the mobile application to be available to the mobile platform, you must publish it on a web server. The publication process is divided into two parts:

• Infrastructure preparation for operation and initial import of the mobile application configuration (performed once).
• Mobile application configuration update in the prepared infrastructure.

To prepare the infrastructure, click Configuration ‑ Mobile application ‑ Publish…. In the opened dialog box, select the Create a virtual directory on the web server check box. If the check box is not selected, the Name and Directory attributes will be unavailable, and clicking Publish will not create a virtual directory on the web server.

After that, specify the properties of the virtual web server directory:

• Name. Defines the name of the virtual directory. This name will participate in the URL configuration of the mobile application to indicate on the mobile device when creating the infobase.
• Web server. Defines the web server in use. If you are using the Microsoft Internet Information Services web server, you can select the Use operating system authentication on the web server check box.
• Directory. Specifies the physical directory on the hard drive in which the mobile application configuration file will be located as an XML file and where the virtual directory of the web server will be displayed.

Use the Update mobile application when updating database configuration check box to enable/disable automatic update of the mobile application configuration upon database configuration update. If the check box is selected, update is performed.

You can also forcibly update the configuration by clicking Configuration ‑ Mobile applications ‑ Update published application. If the mobile application is not published when this command is called, the publication dialog box described above will be opened.

To perform the publication, click Publish. This triggers the following events:

• If the Create a virtual directory on the web server check box is selected, a virtual directory is created on the web server.
• The directory is created on the hard drive where the virtual directory is displayed.
• We recommend that you export the mobile application configuration to the directory specified in the Catalog attribute of the publication dialog box.
• The system checks whether the database configuration matches the configuration being edited.
• If the infobase configuration does not match the configuration being edited, the system prompts you to update the database configuration. However, this operation is optional if the database configuration is the one to be published.
• The mobile application is checked.
• If there are no errors, the infobase configuration is exported to the file. Otherwise, export is not performed.

The file with the mobile application configuration exported by the Publish... command has a fixed name: 1cema.xml. Search (and update) of this particular file is performed when the Update published application command is executed. When creating a virtual directory, the configuration file (1cema.xml) is set as its (directory) default page. This allows you to specify the URL in abbreviated form in the dialog box for creating an infobase on a mobile device.

The Disable button of the dialog box for mobile application publication cancels the publication. It deletes the virtual directory on the web server and the physical directory.

29.7.3.2. Publication details

A publication directory has the following structure:

• 1cema.xml. Configuration description that contains its name, languages, and required permissions.
• 1Cv8.1CM. File that accelerates the infobase creation process. It contains configuration data.
• If a configuration has add-ins, the publication directory will have the following directory structure (all directories and files are optional):
  • Android
    • <Add-InName>.xml
    • ARM
      • <AddInName>.so
      • <AddInName>.apk
    • ARM64
      • <AddInName>.so
      • <AddInName>.apk
    • i386
      • <AddInName>.so
      • <AddInName>.apk
    • x86_64
      • <AddInName>.so
      • <AddInName>.apk
  • iOS
    • <Add-InName>.xml
    • Universal
      • <AddInName>.a
      • <AddInName>.dylib
  • WindowsRuntime
    • <Add-InName>.xml
    • ARM
      • <AddInName>.dll
    • i386
      • <AddInName>.dll
    • x86_64
      • <AddInName>.dll

If a configuration has several add-ins, the publication directory (in any relevant directory structure) will have unique file sets whose number matches the one of configuration add-ins.

All files created as a result of publication are deemed integral part of the published configuration. Deletion, relocation, or renaming of files will result in abnormal performance of the published configuration.

To ensure normal operation of the published configuration, make sure that the web server has registered MIME types for the following extensions:

• Performed by Designer upon publication:
  • .xml: application/xml.
  • .1CM: application/octet-stream.
• Manual registration is required if add-ins must be debugged:
  • .so: application/octet-stream.
  • .apk: application/octet-stream.

<< Prev   Next >>