Architecture Oracle Fusion Middleware Online Documentation Library

8-4 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager app1Group and the application with an AppId of appId2 has been assigned the Organization ID of app2Group.

8.4 Customizing User Interface Branding

The OAAM Server user interface branding is customized in several ways. ■ Custom header footer files ■ Custom CSS file ■ Custom properties for page content and messaging

8.4.1 Custom Header Footer

OAAM Server provides the ability to create custom header and footer files for applications being secured. The header and footer files are JSP and can contain any HTML or JSP code required to replicate the look of the application being secured. All the customer resources JSP files, image files, HTML, and others should be copied into the deployed application directories along with the OAAM Server Web application. The header header.jsp and footer footer.jsp files should contain only content html, all page related tags html, head, body, and so on are already provided by OAAM Server. As a simple example, a header and footer are created that contain a single image each, to be used as the header and footer of an application called appId1. Copy the following code into a file called header.jsp for the header. clientapp1header.jsp img src=clientapp1imagesheader.jpg alt=Welcome to App1 Copy the following code into a file called footer.jsp for the footer. clientapp1footer.jsp img src=clientapp1imagesfooter.jsp alt=App1 Footer These files will be housed in the clientapp1 directory within the Web application. To associate these files with the application you would add the following properties to client_resource_locale.properties: bharosa.uio.appId1.header = clientapp1header.jsp bharosa.uio.appId1.footer = clientapp1footer.jsp

8.4.2 Custom CSS

OAAM Server styles are controlled through a single CSS file, bharosa_uio.css, located in the css directory. These styles can be overridden by including a custom CSS file. Much like the header and footer example show previously, you can create your own file and include that file on an application or global level through properties. Refer to Section 8.5, Configuring Application Properties. In this example you will override the font-family of the default body style definition. The body style in bharosa_uio.css is defined as follows: body{ background-color:ffffff; font-size:12px; color:000000; Customizing the OAAM Server 8-5 font-family:arial,helvetica,sans-serif; margin:0px 0px 0px 0px } Now to use your newly created file, you will add the following property to bharosa_ server.properties: bharosa.uio.appId1.custom.css=clientapp1cssapp1.css In this case, all you did was change Helvetica to the primary font-family in your appId1 application. Any style defined in bharosa_uio.css can be overridden in this manner if required.

8.4.3 Custom Content and Messaging

OAAM Server pages have a variety of content and messaging sections. These sections can be customized by properties in client_resource_locale.properties. Some customizable items, like page title and message, are applicable for each page. While other items, like login blocked message, are specific to a particular page. To change the page title on the login page in the example appId1 application, you would add the following line to client_resource_locale.properties. To change the page title on the login page in the example appId1 application, you would add the following line to client_resource_locale.properties. bharosa.uio.appId1.signon.page.title=Welcome to App1, please sign in. The contents of error messages are also controlled in the same way. In the following example you will customize the error message displayed when a user has been blocked by security rules. bharosa.uio.appId1.login.user.blocked = You are not authorized to login. Please contact customer service at 1-888-555-1234.

8.5 Configuring Application Properties

An application in OAAM Server is made up of a grouping or set of properties. You can configure OAAM Server properties on a global or application specific level. OAAM Server property names are prefixed with bharosa.uio. They are followed by the Application ID or default if the setting is global. An application-level property is one that only effects a single application when there are more than one application defined in the properties. For example, Global or Default header and footer definitions - Apply to all applications that dont specifically define their own bharosa.uio.default.header = globalHeader.jsp bharosa.uio.default.footer = globalFooter.jsp Application specific definitions - These values override the default settings bharosa.uio.app1.header = app1Header.jsp bharosa.uio.app1.footer = app1Footer.jsp bharosa.uio.app2.footer = app2Footer.jsp