Configuration Checklist by Action Type

5-6 Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition The action saved to the catalog stores the reference to the WSDL as: http:[webservicehost]MyWebServicemyservice.wsdl When this action is invoked, the Action Framework substitutes the alias for the actual value before invoking the service. The Administrator can later change the actual element value within the location-alias element so that the saved action points to a different URL without requiring an update the action. An alias can refer to the server and the application path. Therefore, the following example is also valid. Note that the alias should not include the full path to the target WSDL. location-alias aliaswebservicehostalias actualmyserver.oracle.com:7001MyWebServiceactual location-alias

5.3.2 Registries

This topic describes the registry element. A registry defines how the Action Framework should access a browsable library of action targets. For more information about action types and their configuration requirements, see Section 5.2, Overview of the Action Framework Configuration . You can create registry definitions to support the following action types: ■ Navigate to Oracle’s Hyperion Enterprise Performance Management EPM content ■ Invoke a Web Service ■ Invoke a Java Method EJB

5.3.2.1 Navigate to EPM Content Action Type Registry Example

The Hyperion registry contains no additional elements beyond the standard registry elements. The location element should be used to define the Hyperion URL to interrogate. You will need to specify an account with access to the Hyperion targets. The following example is an entry for an EPM content action type. See Table 5–4, Registry Entry Elements and Descriptions for a description of each element. registry idHDPregid nameHyperion Directory Providername content-typeepmcontent-type provider-classoracle.bi.action.registry.epm.HDPRegistry provider-class descriptionHyperion Financial Reports Registrydescription location pathhttp:epms.oracle.com:1901workspacebrowselistXMLpath location service-access accountEPMaccount service-access registry

5.3.2.2 Invoke a Java Method Action Type Registry Example

The following example is an entry for an EJB registry of Java methods. The ejb-targets element, which is embedded within the custom-config element, tells the EJB registry Using Actions to Integrate Oracle BI EE with External Systems 5-7 specifically about the application server hosting the EJBs and the EJBs that should be exposed as registries from that server. See Table 5–4, Registry Entry Elements and Descriptions for a description of each element. registry idreg03id nameSample EJBsname content-typejavacontent-type provider-classoracle.bi.action.registry.java.EJBRegistryprovider-class descriptionCustom Java classes which can be invoked as action targetsdescription location path location custom-config ejb-targets appserver context-factoryweblogic.jndi.WLInitialContextFactory context-factory jndi-urlt3:localhost:9704jndi-url server-namelocalhostserver-name accountWLSJNDIaccount ejb-excludemgmtejb-exclude ejb-excludePopulationServiceBeanejb-exclude appserver ejb-app serverlocalhostserver app-contextActionSamplesEJBapp-context ejb-app ejb-targets custom-config registry

5.3.2.3 Invoke a Web Service Action Type Registry Example

The following example is an entry for a WSIL registry of Web Services. See Table 5–4, Registry Entry Elements and Descriptions for a description of each element. registry idreg1id nameSample Web Servicesname content-typewebservicescontent-type provider-classoracle.bi.action.registry.wsil.WSILRegistryprovider-class descriptiondescription location pathhttp:localhost:9704ActionSamplesinspection.wsilpath location service-access pathSample Web ServicesRating Servicepath policySAMLPolicypolicy propagateIdentitytruepropagateIdentity service-access service-access pathSample Web ServicesCustomer Rating Servicepath accountPayrollUseraccount policyuserNamePolicypolicy propagateIdentityfalsepropagateIdentity service-access registry