1. Building a Deployment The following screens demonstrate how to: 1. Create a new OpenHRE™ tailor-made deployment using a remote (sample) deployment Standard deployment is used as an example 2. Modify newly created, tailor-made deployment using remote (sample) snippets UK English settings snippet and IHE partners snippet are used as examples 3. Manually adjust settings of the newly created, tailor-made deployment 4. Deploy OpenHRE™ based on a newly created, tailor-made deployment To the local directory To the target system (running OpenHRE™ Release Node)

2. Creating a New Deployment (1/6) Log-in, Deployments Library, Copy of a remote deployment

3. To access the Deployment Management UI application, in a web browser, enter https:// :8081 and press ENTER. Note: You must use a secure SSL connection to access the system.

4. To access Deployment Management, enter the appropriate information in the User name and the Password fields and click the Log in button.

5. To access deployments, click the Deployments tab. List of local deployments displays. Note: Local deployments are prefixed with local@. Note: Release drop-down lists are prefilled with the latest release available on the Release Server. Select a release and sub-release in the Release drop-down list to specify the release that is preloaded on the Release Server. Specified release is used - to provide remote snippets (examples of the snippets) for Deployment Management - to provide remote deployments (examples of the deployments) for Deployment Management - as a source of binaries to deploy OpenHRE TM.

6. Select the Show remote deployments check box to display examples of deployments for a selected release. To access a non-editable deployment example, select the Standard deployment check box. Note: Remote (sample) deployments are not prefixed with local@.

7. To create a local copy of the Standard deployment that serves you as an editable, customer-specific deployment, click the Copy button.

8. Note: There is a postfix _copy added at the end of the Id field. Enter the appropriate information in the Id field to change it. Note: There is a postfix Copy added at the end of the Name field. Enter the appropriate information in the Name field to change it. To create a local copy of the Standard deployment, click the Copy button.

9. Note: You are now maintaining a newly created local copy of the Standard deployment.

10. Using Snippets (2/6) Modifications of the local deployment using prepared snippets

11. Local deployment Snippets changes

12. To review your prepared local snippets, together with the remote snippets provided by the selected OpenHRE TM release, click the Snippets tab.

13. To add the UK language support, select UK English settings snippet.

14. The UK English settings option Appears in the list of snippets.

15. To display configurations for UK English, click the UK English settings snippet. Note: In order to make changes to the snippets you have to navigate to the snippets library. When editing a deployment, the snippets are only being added or removed.

16. Using Class Snippets (3/6) Modifications of the local deployment using prepared class snippets

17. Local deployment Classes changes

18. To review your prepared local class snippets, together with the remote class snippets provided by the selected OpenHRE TM release, click the Classes tab.

19. To add the XDS/PDQ v3 partner installed on the VM21 server, select the VM21 XDS/PDQ v3 partner snippet.

20. To display the VM21 XDS/PDQ v3 partner snippet configuration, click the corresponding snippet link.

21. To add the XCA/XCPD partner installed on the VM21 server, select the VM21 XCA/XCPD partner snippet.

22. To display the VM21 XCA/XCPD partner snippet configuration, click the snippet link. Note: In order to make changes to the class snippets you have to navigate to the snippets library. When editing a deployment, the class snippets are only being added or removed.

23. Manual Adjustments (4/6) Modifications of the local deployment by manually adjusting modules

24. Local deployment Modules changes

25. To review the Standard deployment selected modules, click the Modules tab.

26. To review and edit a module, select the E-mail Messaging module.

27. For example, enter the required e-mail address in the appropriate fields. ● E-mail addresses for alerts notifications ● E-mail addresses for exceptions notifications

28. To reach the end of the list of module parameters, scroll down the page. To save the changes to the editable and customized local deployment, click the Save button.

29. Manual Deployment to a Directory (5/6) Deployment of the configured instance to the server directory

30. Local deployment Deployment to the server directory

31. To deploy a release to the directory, click the Target drop-down list and select a server directory.

32. To select an operating system for the target system, click the OS (Operating System) drop-down list, select the target operating system, and click Deploy button. Note: A ready-to-run configured deployment can be found in the preconfigured directory on the configuration server. You can them simply manually transfer the directory with the created deployment to the target server, and start up the system there.

33. Windows Deployment Layout Linux Deployment Layout

34. Remote Deployment to a Server (6/6) Deployment of the configured instance to the target server running OpenHRE™ Release Node

35. Local deployment Deployment to the target server running OpenHRE™ Release Node

36. To deploy a release to the target server, click the Target drop-down list and select the target server. Note: The Target drop-down list also displays the target server status [running/stopped] and deployed version. Note: In order to perform remote deployments and to remotely control the running server instance, the target server must be running OpenHRE™ Release Node application, and the connection to the remote server must be configured in the Deployment Management configuration.

37. Note: If the target server OpenHRE TM is running, the Stop button to stop the target OpenHRE TM displays. To stop the target system OpenHRE TM, click the Stop button.

38. Note: If the OpenHRE TM target server is not running, click the Start button to start the OpenHRE TM target and click the Deploy button to deploy the deployment display. Click the Start button to start or click the Deploy button to deploy the target system OpenHRE TM.

39. To display a log from the last OpenHRE TM activity, click the Show log link.

41. Summary After creating a new deployment (either from scratch or as a copy of an existing one), the set of needed modules is selected. For rapid application of a typical configuration some of the prepared snippets can be added to the deployment, overriding the default values of singleton modules. Snippets represent configuration of typical use cases. Prepared class snippets are added to the deployment to include configured instances of class modules (e.g., external partners, tunnels, server endpoints, etc.). Manual adjustments of a deployment take the highest priority, overriding thus the default values of the modules and the values provided by snippets. Prepared configuration can be deployed into a directory (for a manual transfer and installation), or sent to a target server and started remotely.