Professional Documents
Culture Documents
9.3.0.1 Planning
Start up
• Check the BPMA Services – Hyperion Process Manager, Hyperion BPMA Web
• Check that the default website is started – Administrative Tools/IIS Manager.
• Right click on Default Website/Properties and make sure the ASP.NET tab shows 2.xxx (and
not 1.xxx)
• For Win2K3 specific OS – In Administrative Tools/IIS Manager select Extensions and make
sure .Net extension is authorized
• Make sure user has App Creator and Dimension Editor roles provisioned in HSS
Clean up (Planning):
• In order to clean up manually after an un-successful deployment and re-deploy the app you
need to make sure that this application doesn’t already exist in Essbase (if it does, delete it
manually.)
• Make sure that the relational tables didn’t get created in the relational database. If they did,
delete and re-create the relational database. - If you try to delete just the relational tables,
you’ll get all sort of dependency errors and you need to keep selecting the tables and deleting
until they are all gone.
• Make sure that in your planning system database there is no row for this application in the
HSPSYS_APPLICATIONS table, in HSPSYS_DATASOURCES take a look at the app_id
value in the data source you are using for this app and remember it. Change it to -1. Go to
HSPSYS_PROPERTIES table and delete all rows with object_id = to the above app_id
value. Re-start the Planning app server.
1/2
2/11/2011
o If the file in this directory is up-to-date, you may want to copy/paste this file over the
one located on the mapped port.
Useful Links:
Technical Specifications:
• IIS is being used by Dimension Server and the .NET related Web Services layer. The BPMA
Web Tier invokes .NET Web Services provided by IIS for Data Access and Dimension Server
Services.
• Web application servers ( WebLogic, WebShpere, Tomcat)
• BPMA Web Tier has a requirement of being hosted on an App Server (without J2EE) could
be Tomcat, WebLogic or Websphere. For Data Synch, there is a requirement for J2EE
component because of the dependence on the AXIS Servlet engine and AXIS based Web
Services.
• BPMA Relational repositories: MS SQL, Oracle, DB2)
• How does IIS interact with Web App Server
o All Calls from the Web Tier/Presentation tier happens through .NET based Web
Services, the .NET based Web Services are SOAP based calls between the Web
Tier/Presentation tier and IIS. Dimension Server C# APIs are wrapped in .NET Web
Services for all Dimension Server functionality.
• Logs files (names, locations, how to read)
o C:\Hyperion\BPMA\AppServer\InstalledApps\Tomcat\5.0.28\BPMAWebServer\webap
ps\awb\WEB-INF\log\awb.log ( for all BPMA Web/Apps Tier Logging)
o Location configurable by Log4J properties (file AWBLog4j.properties)
o C:\Hyperion\BPMA\AppServer\InstalledApps\Tomcat\5.0.28\BPMAWebServer\webap
ps\awb\WEB-INF\conf\ AwbLog4j.properties
• Config and/or property files (names, locations)
o AWBConfig.properties : has info for SSO, Dim Server etc.
o BPMA_Server_Config.xml has all information related to Dim Server configuration and
is located under \AppTier\DimensionServer\process_manager_service.
o C:\Hyperion\BPMA\AppServer\DimensionServer\ServerEngine\bin\BPMA_Server_Co
nfig.xml
o C:\Hyperion\BPMA\AppServer\InstalledApps\Tomcat\5.0.28\BPMAWebServer\webap
ps\awb\WEB-INF\conf\ AWBConfig.properties
o C:\Hyperion\BPMA\AppServer\InstalledApps\Tomcat\5.0.28\BPMAWebServer\webap
ps\awb\WEB-INF\conf\ BPMServer.properties
o C:\Hyperion\BPMA\AppServer\InstalledApps\Tomcat\5.0.28\BPMAWebServer\webap
ps\awb\WEB-INF\conf\ AWBCluster.xml
o Note: Paths are slightly different for each Application Server (Tomcat, WebLogic,
WebSphere), but the file names are the same.
2/2