SystemConfigure a Destination Server (Indirect Access)

If the source server cannot directly access the destination server, then object promotionClosed The transfer of a copy of objects specified in a promotion configuration from one Loftware Application Server to another. must be performed by using indirect access. Before you can promote objects from one Loftware Application Server to another using indirect access, you must configure the destination server to be able to receive objects for promotion.

Configure Event Integration to Import Objects for Promotion

To support object promotion performed using indirect access, you must create an Event File Consumer integration on the destination server to receive data files from source servers. This type of Event integration imports data into Loftware Enterprise SP from compressed data files saved in a specific folder.

To configure a destination server to accept data files containing objects to be promoted, perform the following steps.

Note: To perform this task, you must be signed in as the SystemAdmin or SuperAdmin user. For more information, see Controlling Access to System Settings.

  1. On the destination server or a server accessible to it, in the operating system create a folder into which administrators can drop compressed files containing objects to be promoted. It is suggested that you name this folder Promote.

    Note: This folder must be accessible by the Loftware Spectrum service running on the destination server. Files should not be edited in this folder.

  2. Sign in to Loftware Enterprise SP on the destination server using an account with the permissions necessary to create integrations.
  3. In Integrations Integrations, click New > Event File Consumer.
  4. In the Basic Configuration panel, configure the following.
    1. For the Directory Name, enter the path to the operating system folder that you created to receive compressed files containing objects to be promoted. It is suggested that you name the folder Promote.
      • If it is a shared folder, you can enter the name as a UNC path, such as \\Server01\Promote.
      • If it is a folder on the destination server, you can enter the name as a local folder name, such as C:\Promote or /opt/loftware/Promote.
    2. For Run As, select the Loftware Enterprise SP user account under which requests received from outside Loftware Enterprise SP are run. This user account must have at least the INTEGRATOR role or equivalent permissions and is typically not an interactive user. For more information, see Configuring a Run As User for Integrations.

      Tip: Users who promote or import label templates, applications, business rules, forms, images, layer objects, layouts, reusable objects, or workflow templates should have Create permission for Documents and Write permission for Documents on the destination server. Likewise, users who promote or import other types of objects should have Create permission and Write Permission for the relevant object types. Create permission is required for promoting or importing into a folder where an object of the same name does not exist. Write permission is required for promoting or importing into a folder where an object of the same name already exists.

  5. Click the Processors panel, and then configure the following.
    1. In the Available Processors list, click Transformation, and then click Add Before.
    2. With the Transformation processor selected in the Configured Processors list, click the Main Script panel.
    3. For Output Type, select Not Set.
    4. In the text box, enter the following script:

      importPromotionFromFile(getMessageBody(1));

  6. Click Save Save to save the integration. It is suggested that you name the integration Promote Integration.
  7. Click Start Integration.
  8. In the Properties pane, confirm that the Status of the integration is Service Up.

Tip: You should provide the drop folder path to any administrators who are expected to use it to promote objects.

The drop folder is ready to receive compressed files containing objects to be promoted.

Configure Permissions for Folders to Receive Imported Objects

To support object promotion performed using indirect access, you must configure the object access permissionsClosed Permissions in Loftware associated with a specific object or with a folder that control what actions can be performed on that object or on objects within that folder. Each object has default permissions that can be overridden by exceptions for a specific group or user. A user must have both a role-based permission and the corresponding object access permission to perform an action on an object. for folders in Loftware Enterprise SP on the destination server to allow them to receive objects imported by using an integration.

The following object access permissions are typically necessary to support integrations. Additional permissions may be required to support some processes and business rules.

  • Folders containing device groups to be used in conjunction with an integration should grant the group that you create for Run As users Read and Print permissions for Device Groups.
  • Folders containing label templates, layouts, images, or business rules to be used when printing via an integration should grant that group Read and Print permissions for Documents.
  • Folders containing processes used by integrations should grant that group Read and Print permissions for Processes.

For more information about configuring users and groups and about granting access to objects, see Getting Started with Users and Permissions.

If you want to configure a destination server to automatically publish promoted objects upon import, see the following section. Otherwise, when you are ready to select objects to be promoted from a source server to this destination server, see Create a Promotion Configuration (Indirect Access).

Configure Automatic Publishing (Optional)

Although not required, you can configure a destination server to automatically publish all promoted objects without review when they are received. This configuration is appropriate only for destination servers used for a phase of development in which there is no need to review promoted objects prior to publishing them.

Example

A typical organization's development process includes development, quality assurance (QA), user acceptance testing (UAT), and production phases. The organization decides that automatic publishing would not be appropriate for the QA server where functional testing is performed because it is necessary to review objects promoted from development before publishing them. However, the organization's development process does not include any review of objects during the UAT phase until after they are published, so the organization decides that automatic publishing is appropriate for the UAT server.

If you want to turn on automatic publishing of all objects when promoted to a particular destination server, on that Loftware Application Server modify the Loftware Enterprise SP system property progression.import.auto.publish to set its value to true. For information about viewing and modifying a system property, see View and Update System Properties.

Note: To perform this task, you must be signed in as the SystemAdmin or SuperAdmin user. For more information, see Controlling Access to System Settings.

Note: Changing the value of this system property has no effect on progressions or any other aspect of workflows.

After you have turned on automatic publishing on a Loftware Application Server, all objects promoted to this destination server are automatically published upon promotion. For objects promoted to this server by using indirect access, the promoted objects are published upon import to this server. Objects promoted prior to turning on automatic publishing are not affected.

When you are ready to select objects to be promoted from a source server to this destination server, see Create a Promotion Configuration (Indirect Access).