Migrating Objects with the Promotion Module
The Promotion Module is used to migrate Redwood Server objects from one environment into another. The module features three object types, import and export rule sets as well as remote systems. Export rule sets are used to specify which objects are to be exported. Import rule sets are used to adapt the objects to the new environment, like changing the default value of parameters, for example. Remote systems are used to stream-line promotion of objects between environments. You promote objects from development to test from the context-menu of the object by selecting the remote system's name.
Process Definitions
The module ships with the following process definitions
- System_APP_Install - Installs signed CAR files
- System_APP_Uninstall - Uninstalls signed CAR files
- System_Export_Application - Exports an application
- System_Export_RuleSet - Exports objects as defined in an export rule set
- System_Import_Archive - Imports definitions from a Redwood Server Archive (CAR)
- System_Import_Archive_WithApproval - Imports definitions from a Redwood Server Archive (CAR) once approval has been obtained via an operator message
- System_Import_JarFile - Imports Java archives (JAR) into a library
- System_Import_Settings - Sets import settings used by System_Import_Archive
- System_Import_SystemCarFiles - Imports system supplied Cronacle Archive (CAR) definitions
- System_Import_ThirdParty_Plugin - Starts the import of data from third parties into Redwood Server
- System_Promote - Promotes CAR files to remote systems
- System_Promote_Further - Promotes a recently imported CAR file to another remote system
The Import Third Party Scheduler Data functionality is provided for Product Consultants to import data from third-party scheduling solutions.
Promoting Objects from and to Remote Systems
You create a remote system of type Source or Both in the target system pointing at the source Redwood Server URL; the remote system would be pointing, for example, at your development system. Likewise you create a remote system of type Destination or Both in your source system pointing, for example, at your production system.
The source system needs to be able to access the target system on the port of the application server and needs valid credentials for a user that has sufficient privileges to import objects and create the objects to be imported.
note
It is recommended to edit objects in the development environment only and to test these changes in the test environment; several iterations are usually necessary. Once you are happy with the results, you promote the objects from test further into production. No object changes should be carried out in your Test environment; this way you keep your test environment clean of any changes that may later impact your production environment.
Configuration
You customize the promotion module using the following registry entries:
/configuration/import/RunAsUser- the subject to use for the import process, if this is not set, the owner of the System_Import_Archive will be used./configuration/import/LockDown- if this is set totrue, only specific source systems are allowed./configuration/export/name- the originator ID that is used to match the Source or Both remote system object in the target system.
You set the first two registry entries either manually or with the System_Import_Settings process. The last registry entry above can only be set manually.
Promote Further Pusher, Pusher Acceptor and Pusher Processes
You create specific processes that are called when you promote an object to another system (Pusher & Promote Further Pusher) or when a promoted object is received (Pusher Acceptor). You can use the processes to ensure all criteria are met for promotion, for example.
Pusher and Promote Further Pusher must submit System_Promote and System_Promote_Further, respectively, to do the actual work of promoting the export rule set/car file (again, respectively). Pusher Acceptor processes allow the import by default; so for these you have to design the logic and fail the process in cases where you want to overrule the promotion.
See Reaction Processes for more information.
Promotion Module SAP CTS Integration
You integrate Redwood Server promotion into your SAP CTS+ landscape by installing a set of scripts on your SAP system; see Integrating Redwood Server Promotion into SAP CTS and Pusher Process Definition for SAP CTS+ Integration for more information.