In this blog, which is the final one that covers the install of Hyperion EPM in a distributed environment in Oracle VirtualBox. In this blog, we would be configuring the web server once again and testing if we can access the environment.
Understanding why web server needs to be configured once again after all the servers in the distributed environment are configured. If you observed the above snapshots, you would have noticed that the Java web application are configured on different servers. This is the snapshot when we configured the foundation server at start:
Observe that only Foundation components like Workspace, EPMA and HSS are present initially.
This is the deployment of web apps to the Foundation server application server.
After this deployment, to ensure OHS knows the web apps exist, we need to configure it once again.
The configuration is as shown in the below snapshots.
After running the configuration, the next snapshots show us accessing the environment.
This concludes the install of Hyperion EPM in a distributed environment that was created using Oracle VirtualBox.
Understanding why web server needs to be configured once again after all the servers in the distributed environment are configured. If you observed the above snapshots, you would have noticed that the Java web application are configured on different servers. This is the snapshot when we configured the foundation server at start:
Observe that only Foundation components like Workspace, EPMA and HSS are present initially.
This is the deployment of web apps to the Foundation server application server.
After this deployment, to ensure OHS knows the web apps exist, we need to configure it once again.
The configuration is as shown in the below snapshots.
After running the configuration, the next snapshots show us accessing the environment.
This concludes the install of Hyperion EPM in a distributed environment that was created using Oracle VirtualBox.
No comments:
Post a Comment