In order to load more than one configuration element at once, one can make use of the Import Archive button. When clicking the button, a dialog offers the user the option to select the archive file and then a panel where all properties- or ini-files associated with the archive are shown.

You can select single files to be loaded and assign Machine, Instance Type and Instance Name.

To import the elements as common elements, the Import as private elements checkbox must be unchecked.

 

 

After a user clicks the OK button, all imported property files will appear in the File table and will filter on the main panel of the Configuration Element Editor. Clicking the Apply button will send the elements to the configuration server to be stored in the configuration database.

 

Example

Let’s consider the example to set up a Java Client and an Administration Client as well as exporting the configuration.

Let’s assume that we have Java Client’s and Administration Client’s archives, spclient.jar and adminClient.jar, and the customer specific settings custom.zip and admincustom.zip. Our client machine has been set up with SetupCfg program. In the example, we will configure the Administration Client and the Java Client and export the workspace configuration in order to re-apply it on another configuration server.

 

Note The common configuration elements need to be imported before private configuration elements

 

Import spclient.jar

After that we will have Java Client common configuration ready. It is needed for both Java Client and Administration Client.

Open the configuration editor. Initially, there is no configuration for either Administration Client or Java Client.

 

 

Click the Import Archive button and select spclient.jar from your installation directory.

 

 

Select JavaClient in the Instance Type field, uncheck the Import as private elements checkbox and select the appropriate code page if needed. Then click OK.

 

 

Now the Java Client’s common configuration has been loaded and is ready to be sent to the server by clicking the Apply button in the configuration editor’s main panel.

 

Import custom.zip

Repeat the procedure for custom.zip with the difference that this configuration file needs to be imported as Private, and the Machine field name will be set to Client-1.

 

 

Import adminclient.jar

Import adminclient.jar as Common for AdminClient instance type.

 

 

Now the Administration Client’s common configuration has been loaded.

 

Import admincustom.zip

Repeat the procedure for admincustom.zip with the difference that this configuration must be imported as Private, and the Machine field name will be set to Client-1.

 

 

Add custom configuration (custom.properties and admin.properties)

Now there are two new instance types, AdminClient and JavaClient, and the Client-1 machine added.

 

 

Open a pop-up menu by right mouse button click at the Files table.

 

 

Click Add, and enter custom.properties.

 

 

Fill in the Machine, Instance Type and content of the JavaClient custom configuration.

 

 

Click Save.

Repeat the same for Administration Client’s custom configuration, admin.properties:

 

 

Click Save. Now the configuration elements custom.properties and admin.properties are created.

 

 

Click the Apply button in order to send all the changes to the configuration server.

 

Run and check

Now the Java Client and Administration Client can be started against the central configuration server.

 

---