When Essbase Server is converted to EPM System security mode, applications are automatically registered with Shared Services. You may need to reregister applications in these situations:
If you move an application from a project to Unassigned Applications in the Shared Services Console, you need to reregister it.
If you use MaxL or the API to change the Essbase Administration Serverlocation (used during callback from Shared Services), you need to reregister all applications on Essbase Server.
If you use MaxL or the API to convert Essbase Server to EPM System security mode, you need to reregister all applications on Essbase Server.
If you delete a project in the Shared Services Console, you need reregister all applications in the project. To get the global application back, you need to reregister all applications on Essbase Server.
If the Essbase Administration Server machine name or port number is changed, you need to reregister all applications on Essbase Server.
If the Essbase Server machine name or port number is changed, you need to reregister all applications on Essbase Server.
You do not need to register newly created applications or applications that have been renamed. Those types of changes are automatically propagated to Shared Services.
To reregister an application with Shared Services:
From Enterprise View or a custom view, select the application.
Right-click and select Register.
The application is registered with Shared Services and the Shared Services Console is updated.
To register all applications on Essbase Server with Shared Services:
From Enterprise View or a custom view, select the Applications container node.
Right-click and select Register all.
All applications on Essbase Server are registered with Shared Services and the Shared Services Console is updated.
“User Management and Security in EPM System Security Mode” in the Oracle Essbase Database Administrator's Guide
alter application (MaxL) in the Oracle Essbase Technical Reference