This content has been marked as final. Show 8 replies
Personally I think you steer well clear of EPMA on 9.3, anyway which OS and service pack have you installed on.
Did you configure the apache web server as the last step, if not reconfigure.
Does the following URL return http://<epma_server>:19091/awb/conf/AwbConfig.xml
And this URL http://<epma_server>/hyperion-bpma-server/Sessions.asmx
Well upgrading to 11 is a separate activity for which users cannot give downtime so we will hold out on that for the time being.
Our test server is Windows2003 standard edition, and Service Pack 2 is installed.
Yes, Apache configuration was the last step when we installed reporting and analysis components in the end.
http://<epma_server>:19091/awb/conf/AwbConfig.xml is returning xml
but http://<epma_server>/hyperion-bpma-server/Sessions.asmx gives http 400 bad request error code, page not found.
Yes IIS is running but browing the webpage gives a HTTP Error 403 - Forbidden message, with 'You are not authorized to view this page'.
.net is installed and the asp.net is enabled and the asp pages are set to allowed.
EPMA services start without any errors in the event viewer.
The problem has been taken care of via SR after we contacted Oracle Support.
It was indeed an IIS issue where the virtual directory and related permissions etc where created but not configured correctly. Oracle removed the existing directory, created a new one, granted required permissions and set the correct properties and then reset the IIS.
Worked like a charm =)
Thanks for your input though,
I am not sure of exactly which settings were changed because a number of changes were made by Oracle Support themselves, but the documented steps are as follows.
In our IIS Manager under servername the websites expanded to 'Hyperion' which was our hyperion virtual directory. As per System 9 Installation and Configuration Guide, we need to have EPMA connection pools and Virtual Directories as "hyperion-bpma-server" so they first stopped EPMA services then:
1. Reconfigured EPMA using Configuration utility.
2. Altered the connection pool and Virtual Directories as hyperion-bpma-server
- Our application pool only had DefaultAppPool, so a new pool was created as 'bpma' > 'hyperion-bpma-server'
- The 'Hyperion' virtual directory was deleted, new website was create as 'Default Web Site' with C:\Inetpub\wwwroot as local path. Under 'Default Web Site' a new virtual directory was made as 'hyperion-bpma-server' with local path C:\Hyperion\BPMA\AppServer\DimensionServer\WebService and selected 'bpma' as its application pool.
3. Configured virtual directory settings.
4. Copied bin & temp folders from our Production EPMA server path C:\Hyperion\BPMA\AppServer\DimensionServer\WebService, since these folders did not exist in our test server.
5. Restarted IIS
6. Restarted Web Server(Apache)
7. Started the EPMA Services.
Logged into Workspace and Application Library and Dimension Library were accessible, and we successfully created and deployed our applications.
Hope this is helpful for you.
Edited by: 858772 on Jul 27, 2012 1:15 AM