GridServer Managers support the ability to export the configuration and deployment of Directors and Brokers into a signed JAR file format and later import this same format to another Manager. You can migrate Manager configurations from a UAT or prototype grid to a production grid, simplify administration of multiple Manager systems, or disseminate an organization’s default Manager configuration among all clusters in the organization.
The Import/Export feature imports and exports the following component configurations:
•
Manager configurations
•
Service Types
•
Batches / Batch schedule
•
Service Runners
•
Contents of the internal repository
•
GridCache Schemas
•
Resource files, including Grid Library files
•
Credentials repository
•
Server Hooks
You can only Import/Export the internal repository and Manger Configurations on Managers of the same version and update. For example, if you export a GridServer 5.1 Manager configuration, you can’t import it on a GridServer 6.1 installation.
Warning
Not all Manager configuration items are exportable. Server environment-specific items, such as reporting database configuration, are not exported.
To export a configuration
Procedure
1.
In the GridServer Administration Tool, go to Admin > System Admin > Manager Import/Export.
2.
Select the configurations to include in the JAR. In each configuration group, you can select individual items, or choose Select all to include all items in that group.
3.
Click Export.
4.
A File Download dialog box appears. Click Save to save the JAR file.
To import a configuration
Procedure
1.
Go to Admin > System Admin > Manager Import/Export.
2.
Click the Browse button next to the Provide File for import box.
3.
Browse to the location of the JAR file containing the GridServer Manager configuration export.
4.
Click Upload to begin the import.
5.
A list of configurations found in the JAR file are displayed, with configurations highlighted in red if they install over existing configurations. Select the configurations you want to import, then click Import.
If the Manager requires a restart for changes to take effect, a message is displayed and the Manager automatically shuts down.