Business Service Control Configuration

• Section Paging Limits Oracle Service Registry API Endpoint URL This configuration part contains the endpoint URLs used by the Business Service Control to communicate with Oracle Service Registry: urlhttp:localhost:8888registryurl secureUrlhttps:localhost:8443registrysecureUrl useSoapfalseuseSoap uddiEndpoints accountApiPath=uddiaccount approverApiPath=uddiapprover categoryApiPath=uddicategory configuratorApiPath=uddiconfigurator inquiryPath=uddiinquiryExt inquiryUIApiPath=uddiinquiryUI publishingPath=uddipublishingExt requestorApiPath=uddirequestor securityPath=uddisecurity subscriptionPath=uddisubscriptionExt taxonomyApiPath=udditaxonomy wsdlApiPath=uddiwsdl2uddi xml2UddiApiPath=uddixml2uddi xsd2UddiApiPath=uddixsd2uddi xslt2UddiApiPath=uddixslt2uddi The endpoint URL is composed of two parts: • The prefix, taken from the url element or secureURL element for a secure endpoint • The relative part, taken from the specified uddiEndpoints attribute depending on the type of the endpoint. If you want to use a different target registry, it is usually sufficient to change the prefix the absolute part of the URL. Important The useSoap element indicates whether to use SOAP to access Oracle Service Registry, or to ignore the declared API endpoints and make the calls directly through the Java virtual machine. Result Filtering Use this section to filter data that should not be displayed in the Business Service Control. For example, to hide the Operational business entity, you can set up a filter in the businessUI element. Note that child elements of an element you filter will not be displayed in the Business Service Control. The following sample will hide the Operational business entity in the Business Service Control: filteredKeys businessKeyuddi:systinet.com:uddinodebusinessKeybusinessKey filteredKeys Main Menu Tabs tab tabId=home taskId=home captionKeybsc.tab_homecaptionKey hintKeybsc.tab_homeHinthintKey tab tab tabId=search taskId=search captionKeybsc.tab_searchcaptionKey hintKeybsc.tab_searchHinthintKey tab tab tabId=catalog taskId=publish Page 573 Main Menu Tabs captionKeybsc.tab_catalogcaptionKey hintKeybsc.tab_catalogHinthintKey tab tab tabId=tools taskId=tools captionKeybsc.tab_toolscaptionKey hintKeybsc.tab_toolsHinthintKey tab tab tabId=report taskId=browsecat captionKeybsc.tab_reportscaptionKey hintKeybsc.tab_reportsHinthintKey tab tab tabId=configure taskId=configure captionKeybsc.tab_configurecaptionKey hintKeybsc.tab_configureHinthintKey tab Each tab element contains the definition of one main menu tab. These tabs are rendered in the top left area of the Business Service Control, under the product logo. Important Some navigation tabs should not be visible in all cases. Tab visibility depends on the profile selected for the current user. The Oracle Service Registry administrator should define tab visibility using the Configuration main menu tab. Table 89. Tab element attributes Required Description Attribute yes Resource bundle key to caption visible for users. captionKey yes Unique tab identification. tabId yes URI of the task called when a user clicks on this tab. taskId no Resource bundle key to descriptive text displayed as tab tooltip. hintKey User Profiles profile defaultTab=home profileId=default captionKey=bsc.profile_anonymousUserProfile visibleTabsearchvisibleTab visibleTabreportvisibleTab visibleTabhomevisibleTab defaultView viewId=Common viewType=providers defaultView viewId=Common viewType=interfaces defaultView viewId=Common viewType=endpoints defaultView viewId=Common viewType=bindings defaultView viewId=Common viewType=services profile Each profile element contains the definition of one user profile. The user profile defines the visibility of tabs, default navigation tab, and default views for various Business Service Control entity lists. Users are able to change their profiles using the My Profile link from the Home page, unless an administrator has prohibited this via the Configure tab. Page 574 User Profiles Table 90. Profile Element Attributes Required Description Attribute yes Tab caption visible for users. caption yes Unique profile identification. profileId yes TabId of the tab which will be displayed after user login. This attribute must contain the identification of one of the visible tabs defined for this profile. defaultTab at least one Id of navigation which will be visible for this user profile. visibleTab one for each viewType Specifies the viewId of the view used as default when the user enters a page with a result list. The attribute viewType defines the type of list and viewId defines view identification. defaultView Entity List Views -- list of available views -- view captionKey=bsc.view_business viewId=Business view captionKey=bsc.view_common viewId=Common view captionKey=bsc.view_technical viewId=Technical view captionKey=bsc.view_operation viewId=Operation -- list of available view types -- viewType captionKey=bsc.viewType_providers viewTypeId=providers viewType captionKey=bsc.viewType_services viewTypeId=services viewType captionKey=bsc.viewType_endpoints viewTypeId=endpoints viewType captionKey=bsc.viewType_interfaces viewTypeId=interfaces viewType captionKey=bsc.viewType_bindings viewTypeId=bindings The view element defines a list of available views. The viewType element defines a list of available entity list types. Important The viewId and viewType values are used to determine which component will be used for view presentation. The Business Service Control automatically checks the existence of all available view components, and only existing views will be presented to user. The View component name has the following format: [viewType][viewId]Results . For example, the component rendering the business view on a list of providers is named providersBusinessResults Browsable Taxonomies browsableTaxonomy captionKey=bsc.browsableTaxonomy_usage tModelKey=uddi:systinet.com:taxonomy:usage browsableTaxonomy captionKey=bsc.browsableTaxonomy_endpoint tModelKey=uddi:systinet.com:taxonomy:endpoint:status browsableTaxonomy captionKey=bsc.browsableTaxonomy_status tModelKey=uddi:systinet.com:taxonomy:interface:status browsableTaxonomy captionKey=bsc.browsableTaxonomy_namespace tModelKey=uddi:uddi.org:xml:namespace browsableTaxonomy captionKey=bsc.browsableTaxonomy_localName tModelKey=uddi:uddi.org:xml:localName browsableTaxonomy captionKey=bsc.browsableTaxonomy_certification tModelKey=uddi:systinet.com:taxonomy:service:certification Page 575 Browsable Taxonomies browsableTaxonomy captionKey=bsc.browsableTaxonomy_availability tModelKey=uddi:systinet.com:taxonomy:endpoint:availability browsableTaxonomy captionKey=bsc.browsableTaxonomy_wsiCompliance tModelKey=uddi:65719168- 72c6-3f29-8c20-62defb0961c0 browsableTaxonomy captionKey=bsc.browsableTaxonomy_milestone tModelKey=uddi:systinet.com:versioning:milestone browsableTaxonomy captionKey=bsc.browsableTaxonomy_releaseDate tModelKey=uddi:systinet.com:versioning:releasedate browsableTaxonomy captionKey=bsc.browsableTaxonomy_version tModelKey=uddi:systinet.com:versioning:version This section holds information about the list of browsable taxonomies. Each taxonomy is displayed as one node in the Business Service Control Reports tab. This list is also used when displaying the Classifications tab on entity detail pages. Table 91. BrowsableTaxonomy Attributes Required Description Attribute yes Taxonomy display name used when rendering the navigation tree on the Report tab. caption yes The key of the taxonomical tModel in Oracle Service Registry. tModelKey Paging Limits pagingLimits component=resourcesXsltResults pageSize=10 pageCount=20 pagingLimits component=resourcesWsdlResults pageSize=10 pageCount=20 pagingLimits component=default pageSize=10 pageCount=20 In this section, the limits of rows displayed on one page and the number of pages displayed are defined. Each component should define its specific settings, or that default values are used when settings are not found.

3.8.4. Entity Configuration

In this section, we will explain how the Business Service Control can be configured to recognize UDDI data as Business Service Control Entities and how to hook into standard actions for those entities. Overview The UDDI specification recognizes 4 entity types. However Business Service Control needs to present the UDDI data in terms of the users business. Because of various mappings of resources, business artifacts etc. to UDDI, a single UDDI entity may correspond to several business-level entities. The Entity Configuration defines how to recognize individual business artifacts. UDDI categorization is used to annotate the UDDI data with information about their role or type. So for example, a tModel is just a resource for the Business Service Control GUI. But when the tModel contains, for example, the uddi:uddi.org:resource:type category with value xslt, it represents an XSL Transformation document. Depending on business needs for the artifacts, different presentations, actions, or relationships may be available. The Entity Configuration further specifies Views to be used for the particular entity. A View is a web page, or a portion of it, customized for the particular Entity. Views correspond to abstract operations that make sense on several entities. For example, pages for Delete action are different for Services and Providers but both pages perform the same abstract operation. Page 576 Overview Configuration The configuration is stored in the file confbsc.xml, inside the entityViews element. New Entities can be created by adding new Entity definitions to that configuration, or behaviour of existing Entities can be changed. In this release, we support creation of new Entities and customization of Entities based on tModels TM. The following example shows a commented configuration of a Categorization entity, derived from a tModel. It corresponds to a taxonomy tModel used by the Registry. The individual parts of the configuration will be described below Page 577 Configuration