Where is the right place to include my own JavaScript files?

• Q: Where is it possible to change the text displayed in the page footer? A: The page footer is defined in the file designpageFooter.jsp.

3.8. Business Service Control Framework

This section describes the Business Service Control BSC from the developers point of view. It describes the Business Service Control Framework architecture and configuration, and demonstrates how to customize the console. The Business Service Control implementation and configuration are contained in the JAR file bsc.jar located in directory REGISTRY_HOMEappuddi . This section has the following subsections: Section 3.8.1, Business Service Control Localization How to localize the Business Service Control, or the Registry Control. Section 3.8.2, Directory Structure The directory structure of bsc.jar. Section 3.8.3, Business Service Control Configuration Business Service Control configuration files in bsc.jar. Section 3.8.5, Permission support Features to establish whether users have permission to perform operations. Section 3.8.6, Components and Tags Components and tags in bsc.jar used to develop Business Service Control components.

3.8.1. Business Service Control Localization

Oracle Service Registry is ready for localization. This chapter is focused on localization of web applications such as the Business Service Control and Registry Control. It provides information on Oracle Service Registry localization support and how to write localizable web applications. Basic concepts The localization support is built upon standard Java resource bundles and the JSP formatting tag library. Locale detection The user language-detection routine is invoked for each HTTP request. When the user is logged in, the userAccounts languageCode is used, if it is set. Otherwise the browsers preferred language is used. The system then finds the resource bundle for the chosen locale or uses a default resource bundle, if there is no such localized resource bundle. See the ResourceBundle javadocs for details of the algorithm. The system uses UTF-8 encoding by default, but it can be configured to use a custom locale-encoding mapping in the file web.xml : webFramework encoding map locale=en encoding=UTF-8 map locale=zh encoding=Big5 encoding webFramework Resource bundles There is one resource bundle common to all JSP files serving as a dictionary - com.systinet.uddi.bui.standard.BUIMessages . It contains keys for common words like OK, Cancel or names of entities Provider, Service. Then each top-level directory in the jsp directory has a unique resource bundle for its files Page 567 Resource bundles and subdirectories. The resource bundles for Business Service Control are located within the src directory and are copied to the WASP-INFclasses directory during build phase. Resource keys naming convention The resource key is composed of JSP file name without suffix and an English identifier in camel notation. Capital letters are used to indicate the start of words, instead of a space or underscore. If the JSP file is located in some subdirectory of the top-level directory, the subdirectory name is also encoded in the resource key. For example resources for JSP file s e a r c h i n t e r f a c e s s i m p l e . j s p a r e s t o r e d i n t h e f i l e com.systinet.uddi.bui.standard.component.search.SearchMessages.properties and all keys have the prefix interfaces.simple_. In some configuration files it is necessary to use a custom resource bundle instead of the default bundle. There is a way to encode the custom resource bundle name into the resource key. If the resource key contains the character , then the part before it will be treated as the resource bundle identifier and the rest of the resource key as actual resource key. For example customBundleresourceKey. Localization of Configuration The configuration files are localizable too. For example the file confbsc.xml has texts in the resource bundle com.systinet.uddi.bui.framework.BSCMessages.properties . The attributes like caption and hint have their localizable alternatives captionKey and hintKey, which have precedence over the original attributes providing text. The exception to this rule is the task element in the file confweb_component.xml, where caption attribute has precedence over new captionKey attribute. JSP localization The localization of JSP files uses the standard formatting tag library. Every JSP must start with import of this library and setting of the locale for the current user, if he is logged in. The users language is stored in the session variable userDefaultLanguage . Example 21. Example of localization taglib prefix=fmt uri=http:java.sun.comjstlfmt c:if test={not empty globalSession[userName]} fmt:setLocale value={globalSession[userDefaultLanguage]} scope=page c:if fmt:setBundle basename=com.systinet.uddi.bui.standard.component.search.SearchMessages var=search_Message fmt:message key=interfaces.simple_operationProperty bundle={search_Message} In addition to the full power of the standard formatting library there are several extensions that complement localization needs. ParseResourceKey tag The parseResourceKey tag is used, when the resource key can contain an embedded resource bundle. It detects such a situation and introduces two new variables that will hold the values of resource bundle and resource key to be used. Page 568 ParseResourceKey tag