Configuring an Environmental Policy

1. Add a New Environmental Policy

1. Click Environmental Policies under Policies in the Admin Console navigation. Alternatively, you can access the Environmental Policies page by clicking the View Policies link on a package’s Configuration tab.
   
   Note: To edit settings for an existing policy, select the policy in the Environmental Policies section.
   
   
   Setting an environmental policy
2. Click  in the Environmental Policies section to create a new policy, or click  to create a new policy by duplicating another.
   
   The Environmental Policies section lists the environmental policies available for use. These are listed in the Environmental Policy drop-down list on a package’s Configuration tab. When you select a policy in the list, the Used In section displays the packages that use the policy.
   To remove a policy, select it, and click . Before removing a policy, be sure no packages use the policy.
   To make a policy the default, select it, and click . However, before you can make a policy the default, you must first roll out the policy by promoting it.
3. Enter a title for the environmental policy, and click OK. This title appears in the Environmental Policy drop-down list on a package’s Configuration tab. The title also appears in the Title field of the Selected Environmental Policy section.
   
   The Selected Environmental Policy section allows you to set command line and VM arguments, config.ini properties, and global workspace and software settings.
4. To set command line and VM arguments, click in the respective area, and type the commands. Each argument must be on its own line. You can set arguments specific to an operating system by clicking the appropriate operating system tab and entering the arguments.
   
   To target a specific architecture, add an argument prefix of (x86) or (x86_64). This allows you to target installations on 32-bit or 64-bit architectures, respectively.

2. Set config.ini Properties

1. Click Properties in the Selected Environmental Policy section.
2. To set properties specific to an operating system, clicking the appropriate operating system tab.
3. Click , to add a new property. 
   To edit a property, select it in the list, and click . To delete a property, select it in the list, and click .
   
   
   Configuring properties for an environmental policy

3. Set Global Workspace Tasks

Set workspace tasks for all packages using this environmental policy.

1. Click Workspace in the Selected Environmental Policy section.
2. To set tasks specific to an operating system, clicking the appropriate operating system tab.
3. Click , to add a new task.
   To delete a task, select it in the list, and click . Use the arrows to change task order.
   
   
   Configuring global workspace tasks for an environmental policy

4. Set Global Software Add-ons

Select software to include in all packages using this environmental policy.

1. Click Software in the Selected Environmental Policy section.
2. From the list of available extra software, expand a software list, select the software you want to add, and click .
   
   In the Available Extra Software section, you can select third-party add-ons to include in packages using this policy. Standard add-ons from Eclipse Discovery and others are listed by default and come from the Eclipse Discovery and other packs you installed. Click  to specify software update sites from which to include third-party software. When you choose software from an update site, it is included in the Available Extra Software list. See Importing Third-Party Software for more information.
   
   The Selected Extra Software section lists all software you added from the Available Extra Software section. To remove an item from the list, select the software, and click . To remove multiple software, click . This opens a window that allows you to select multiple software to remove.
   
   
   Selecting extra software for an environmental policy

5. Add Support for Self Signed Certificates

You can upload a custom “cacerts” file from your already configured JVM to allow your self signed certificates to be trusted by Java. With the help of your environment policy you can upload the file that will be installed on the JVMs that get configured for your package as extra software, this will allow all your installed packages to communicate with your Delivery Hub.

Note: You can also add the file at the system level.