Updating References to a Rehosted Essbase Server

  To updated references to a rehosted Essbase Server instance or cluster:

1. In Essbase Studio Console, select Tools, and then Rehost Essbase Connections.

2. In Rehost Essbase Connections, select the connection to rehost under Essbase connections.

   The old cluster name or Essbase host and port number, and, if applicable, data encryption method, are displayed under Host/Port/Encryption in Catalog.

3. Under New Host/Port/Encryption, enter the new cluster name or new host name, port number, and, if applicable, data encryption method.

   Note:

   For Essbase Server clusters, only the cluster name is required. The port number is not required. By default, the new cluster name is displayed in the New Host/Port/Encryption column.

   Use the following syntax:

   • For an Essbase Server instance, no data encryption, enter:

     host:port

   • For an Essbase Server instance, with data encryption, enter:

     host:port:ssl

   • For an Essbase Server cluster, no data encryption, enter:

     cluster_name

4. Optional: Click Test Connection to validate the entry that you made under New Host/Port/Encryption.

   Note:

   Essbase Studio does not validate entries as you enter them. You must click Test Connection to validate the information that you entered in step 3.

5. Select an Update Deployment History option for the currently selected Essbase Server connection:

   • Update the host name and port number for all deployment history—Replaces all old Essbase Server host and port references to the new host and port that you specified in step 3.

     This is the default option.

   • Replicate the last successful deployment history and update the copy only—Makes a copy of the last successful deployment history listing, and then updates the copy with the new host and port information, and the date and time of the rehosting.

     Tip:	When selecting the “Replicate” option, after the update is complete, each rehosted Essbase model displays twice in the Metadata Navigator: once with the old host:port information and once with the new host:port information.

   Note:

   Deployment history is updated only for successfully rehosted Essbase Server connections.

6. Click Update.

7. For the rehosting status of each Essbase Server connection that is rehosted, check the Update Status column in the Rehost Essbase Connections dialog box.

   If the rehost is successful, the Host/Port/Encryption in Catalog column is updated with the new cluster or host and port information and, if applicable, encryption information. If the rehost fails, an error message is displayed.

   Note:

   If other Essbase Server connections have the same old host:port setting, rehosting one instance rehosts all other instances.