Sie sind auf Seite 1von 2

When we deploy Presentation Services Plug-in to an app server, all the themes, images etc are copied to the

context accessible area of the application server.

We have deployed Workspace into Tomcat and hence we have a multitude of workspace related files in the deployed directory. You can see a couple of folders here. themes and thirdparty/bindows/html/themes.

We have completely different set of folders under both the theme folders. That only the bindows one was used (not the workspace native one). Bindows themes are just for Workspace alone(bringing all the components together while using 19000 workspace port). But the individual themes can vary for different products. In the above screenshot we basically had theme_tadpole and theme_tadpole_hc as native workspace themes(workspace as a product). Also, the Bindows specific themes Bpmtadpole and BpmtadpoleHc. Similarly lets look at the ui_themes folder of Hyperion Scorecards

As you see we only have the product specific ones theme_tadpole and theme_tadpole_hc. So, there are a couple of conclusions that we can derive out of this. 1. When customizing the UI of EPM components, the bindows theme as well as the individual product themes should be in sync with each other 2. Ensure that when you have EPM components deployed in multiple machines, all of them get a common UI through the same default theme theme_tadpole. The _hc version of the themes are the high contrast variants of the original themes.

The login screen basically has 2 parts. One is the background color. And the other is the Oracle EPM logo. Whenever we are customizing the EPM workspace, the same customization will have to be done across all the other product component themes as well. The primary reason is each product can be invoked either through the workspace or directly. In either case, we need to ensure that the UI remains the same. To customize the logo, navigate to {HYPERION_HOME}/deployments/<appserver>/<application>/webapps/<application>/(ui_)themes/(t heme_)tadpole/images_global/ In my case, since i am customizing the login of workspace alone, i had to navigate to /u01/app/oracle/hyperion/deployments/Tomcat5/Workspace/webapps/workspace/themes/theme_t adpole/images_global folder. Here you would find a file called logon_panel.gif. This is the image that actually gets rendered in the logon screen. Replace this image with you corporate logo. Ensure that the image size is 298*367 (pixels). Copy the same image over to {HYPERION_HOME}/products/<product>/AppServer/InstalledApps/<application>/(ui_)themes/(them e_)tadpole/images_global the actual product folder was /u01/app/oracle/hyperion/products/Foundation/AppServer/InstalledApps/workspace_static/themes /theme_tadpole/images_global. We need to have the modified style in both the product directory as well as the installed app server directory. Once we have changed the image, the next step is to change the background color. There are 4 places that we need to modify the settings. 1. Global.css file in {HYPERION_HOME}/products/Foundation/AppServer/InstalledApps/workspace_static/themes/theme _tadpole/ - Product Customization 2. Global.css file in {HYPERION_HOME}/deployments/Tomcat5/Workspace/webapps/workspace/themes/theme_tadpole/ Product Customization 3. theme.css file in {HYPERION_HOME}/deployments/Tomcat5/Workspace/webapps/workspace/thirdparty/bindows/thir dparty/ themes/Bpmtadpole 4. theme.css file in {HYPERION_HOME}/products/Foundation/AppServer/InstalledApps/workspace_static/thirdparty/bin dows/ thirdparty/themes/Bpmtadpole Just edit the css files and modify the necessary property (in our case the background color property). The above changes will ensure that you have customized your workspace application as well as the overall workspace. If you have deployed more applications like Planning, Shared Services etc to be accessible through the workspace, the same customizations will have to be done in those components as well

Das könnte Ihnen auch gefallen