You must perform Essbase Server rehosting steps before you perform this step. See Updating References to a Rehosted Essbase Server .
After upgrade, Essbase Server connections and deployed cubes are affected by changes in host, port, or data encryption information for the underlying Essbase Server instances or clusters, or for any Essbase Studio Server instances.
You must update references to those server instances and clusters in Essbase Studio.
Table 36. Updating References to the Essbase Server Host and the Essbase Studio Host
| Task | Reference |
|---|---|
If Essbase Server host and port have been moved to a new location, update Essbase Studio references to the Essbase Server. | Updating Essbase Studio References to a Rehosted Essbase Server |
If the Essbase Studio Server host and port have been moved to a new location and you have deployed applications that point to the earlier release Essbase Studio Server location, update the cube linkage of those deployed applications to point to the new Essbase Studio Server instance. | Updating Cube Linkages |
If Performance Management Architect has been moved to a new location, then for all Performance Management Architect data source connections that point to the earlier release location, edit the connection properties to reflect the new server location. | Updating Essbase Studio References to a Rehosted Performance Management Architect Server or to Text Files Used as Data Sources |
| If text files were moved to a non-default directory, edit the connection properties for any text file connections to point to the new location. | Updating Essbase Studio References to a Rehosted Performance Management Architect Server or to Text Files Used as Data Sources |