Configure a Destination Server (Direct Access)
If the source server can directly access the destination server, then object promotion The transfer of a copy of objects specified in a promotion configuration from one Loftware Application Server to another. can be performed by using direct access. Before you can promote objects from one Loftware Application Server to another by using direct access, you must configure the destination server to permit the source server to promote objects to it.
Object Promotion Whitelist in System
Designate Allowed Source Servers
To support object promotion performed using direct access, on any Loftware Application Server that you want to serve as a destination server, the SystemAdmin or SuperAdmin user must specify which source servers are allowed to promote objects to it.
To configure a destination server to accept promoted objects from source servers, perform the following steps.
Note: To perform this task, you must be signed in as the SystemAdmin or SuperAdmin user. For more information, see
- On the destination server, in System
- For each source server that you want to be able to promote objects to this destination server, perform the following steps.
- Enter the server name of a Loftware Application Server that will serve as a source server.
Note: Enter only the server name (not a URL or IP address) as it appears in Access Control
- Click Add.
- Enter the server name of a Loftware Application Server that will serve as a source server.
The list of approved source servers is displayed for all administrators who have access to System
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
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 (Direct Access).