1. Deployment Management The following screens demonstrate how to: 1. Access and view deployments 2. Create a new local deployment 3. Create and modify a local copy of the remote deployment

2. Terminology ● Deployment is a tailor-made configuration that only includes instances of the modules that are needed for a particular OpenHRE TM installation. ● Singleton Module is a standalone, working system component that provides a set of unique features within the OpenHRE TM system. A deployment can include only one single instance of such a module. Each module has its default configuration, which is modified manually or by snippets. ● Remote Deployment is a non-editable example of deployment provided by a particular OpenHRE TM release. ● Local Deployment is an editable, local deployment created by administrators to match customers OpenHRE TM requirements. Refer to the Deployment Management.pdf documentation for more information about deployments.

3. Accessing the System (1/5) Log-in, Deployments Library

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

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

6. 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 releases are 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.

7. Creating a New Local Deployment (2/5) …from scratch

8. Creating a new local deployment - from scratch

9. The following screens show how to create a new local deployment. To create a deployment, click the Add button.

10. Fill in the Id and Name fields. To create a new, local deployment, c lick the Add button.

11. Note: You are now maintaining a newly created local deployment. To include a particular module in the deployment, select the check box next to a module. Note: Each module has its default configuration, which can by modified manually or by snippets. Refer to following sections for information on how to: ● modify modules manually ● maintain deployment ● create a new deployment as a copy of sample remote deployment.

12. Creating a New Local Deployment (3/5) …as a copy of a sample remote deployment

13. Create a new local deployment - as a copy of a sample remote deployment

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

15. Note: Since you cannot edit remote (sample) deployments, you cannot deselect a module that is already selected and remove the module from the deployment, or select an unselected module and add the module o the deployment. To review the module parameters, select the Module.

16. Note: Since you cannot edit remote (sample) deployments, you can only review the modules and the associated parameters.

17. To reach the end of the list of module parameters, scroll down the page. To create a local copy of the deployment example that serves as an editable, customer-specific deployment, click the Copy button.

18. Note: There is a postfix _copy added at the end of the Id field. To change the setting, enter the appropriate Id field. Note: There is a postfix Copy added at the end of the Name field. To change the setting, enter the appropriate Name field. To create a local copy of the deployment example, click the Copy button.

19. Deployment Maintenance (4/5) Rename, Copy, Delete, …

20. Deployment Maintenance - from deployment section

21. Note: You are now maintaining a newly, created local deployment. To reach the end of the list of modules, scroll down the page.

22. To directly delete a newly created, local deployment and return to the List of deployments, click the Delete button. To create another copy of the newly created local deployment, click the Copy button. To rename the newly created local deployment, click the Rename button.

23. To return to the List of deployments, click the Cancel button, You can also click the Deployment List link to return to the List of deployments. or click the Save button to save changes before returning to the Deployment List. Note: To exit the deployment without saving changes since the previous Save, click the Cancel button or click the Snippet List link.

24. Deployment Configuration (5/5) Including modules and configuring their parameters

25. Deployment Configuration

26. To access and modify a selected module, select the module.

27. The following screens show how to modify a drop-down list type of parameters. For example, to change the default value of the Date Format, click the Date Format drop-down list and select a date format.

28. Changed parameters display in bold with an icon on the right that allows you to return to the default value. The number in square brackets displays how many module parameters were changed but does not contain the default value. Note: To return to default value, click the icon to the right of the parameter.

29. 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.

30. To access and modify a selected module, select the module. The following screens show how to modify the directory type of a parameter. To include a module in the deployment, select the check box next to a module.

31. Note: The MPI customization directory field contains two options: no folder - which specifies that there is no MPI customization as there is no MPI customization directory specified. uk - which specifies that uk is the name of the MPI customization directory. Note: As the prefilled uk directory is a remote (sample) directory, it is not possible to access and modify it. Deployment management allows you to create a new, editable local directory. To add another option to the MPI customization directory drop-down list, complete following steps. - access the system with Deployment Management installed - create the. /configurator/data/localrepo/dirs/mpi/ directory - copy the customization file to the directory or its subdirectory. To find the MPI customization directory, scroll down the page.

32. The new local (prefixed with local@) option displays, representing a new local customization directory.

33. 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.

34. The newly created local deployment displays in the Deployments list.

35. Summary The deployments define which modules and with what configuration should be deployed as a running instance onto a server. They can be created from scratch, or as a copy of and existing (local or remote) deployment. In many deployments the administrator repeatedly configures the same things. Sets of configuration values can be extracted as so-called snippets, as we will demonstrate in the next presentation.