Invoke a Java Method Action Type Registry Example

Using Actions to Integrate Oracle BI EE with External Systems 5-9 policy This element is optional. Use this element for webservices registries only. This element is located within the service-access element and points to a policy defined in the policies section elsewhere in the configuration file. This element is required for accessing target Web Services that define a WS-Security policy. Note that when invoking secured Web Services in this way, you need to correctly configure OWSM to work with Actions. For more information, see Section 5.5.3, Configuring Oracle Web Services Manager . propogateIdentity Use this element for webservices registries only. This element must be set if the policy element is set. This element is located within the service-access element and can be set to true or false. A value of true is valid when used in conjunction with policies that assert identity for example, SAML-based policies to enable propagating the identity of the user who initially invoked the action. If the propagateIdentity element is set to true, the account element becomes redundant and instead the identity of the user who invoked the action for example, in Oracle BI Presentation Services or run as in scheduler is used to invoke the target Web service. Setting this element to true in conjunction with a usernamepassword token policy is not supported. custom-config Use this element for java registries only. This element is used to specify how to access the EJBs on the target application server. ejb-targets Use this element for java registries only. This element defines the application server where EJBs are deployed in the appserver element, and one or more J2EE applications containing EJBs on the specified appserver that is exposed in the ejb-app elements. appserver Use this element for java registries only. This element is located within the ejb-target element and defines the connection and authentication information to connect to the application server where EJBs are deployed. This element contains the following elements: ■ context-factory – This element contains name of the class used to do JNDI lookups for the application server on which the Action Framework Web Services are deployed. You must set this element to weblogic.jndi.WLInitialContextFactory. ■ jndi-url – This element contains the URL used in JNDI lookups to query the JNDI directory on the application server hosting the target EJBs. ■ server-name – This element contains the name used internally to refer back to this appserver element, which is located in the server element of subsequent ejb-app elements. ■ account – This element contains the name of an account defined elsewhere in the configuration file. This element must point to credentials that have sufficient permissions to query the JNDI directory on the application server that is hosting target EJBs. ■ ejb-exclude – This element is used to exclude EJBs or applications from a given application or application server. When the EJB registry finds a match for this value in the JNDI hierarchy, it stops searching for EJBs down that branch of the JNDI tree. ejb-app Use this element for java registries only. This element points to one or more J2EE applications containing EJBs. This element contains the following elements: ■ server - This element’s value needs to match the server-name element located in the appserver element. ■ app-context - This element contains the application context where the target EJBs were deployed. Table 5–4 Cont. Registry Entry Elements and Descriptions Element Description 5-10 Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition

5.3.2.5 Valid Values for the Provider-Class Element

Table 5–5, Provider-Class Element Values contains the valid values for the provider-class element. For more information about the provider-class element, see Table 5–4, Registry Entry Elements and Descriptions .

5.3.3 Content Types

This topic describes the content-type element. Each content-type element provides meta-information about the types of services to which the registries are connecting. The content types provided during installation should not be modified. You can use only the content types shown in the following example: content-types content-type typenamewebservicestypename displaynameWeb Services and BPEL Processesdisplayname actionTypeWebServiceActionTypeactionType content-type content-type typenameepmtypename displaynameHyperion Applicationsdisplayname actionTypeURLActionTypeactionType content-type content-type typenamemisctypename displaynameMixed Servicesdisplayname actionTypeURLActionTypeactionType content-type content-type typenamejavatypename displaynameJava Actionsdisplayname actionTypeJavaActionTypeactionType content-type content-types

5.3.4 Accounts

This topic describes the account element. The account element defines gateway accounts, which are used for authentication to action targets. The registry elements service-access element then references the accounts that you have specified. For more information about the registry section, see Section 5.3.2, Registries . The following example is an account entry. Table 5–6, Account Elements and Descriptions describes each element. account nameSAMLTestname descriptionTest SAML Accountdescription adminonlyfalseadminonly credentialkeySAMLTestcredentialkey Table 5–5 Provider-Class Element Values Related Action Type Content Type SPI Class Navigate to EPM Content EPM oracle.bi.action.registry.epm.HDPRegistry Invoke a Java Method EJB Java oracle.bi.action.registry.java.EJBRegistry Invoke a Web Service Web Services oracle.bi.action.registry.wsil.WSILRegistr y