Invoke a Web Service Action Type Registry Example

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 Using Actions to Integrate Oracle BI EE with External Systems 5-11 credentialmaporacle.bi.actionscredentialmap account

5.3.4.1 Account Elements Descriptions

Table 5–6, Account Elements and Descriptions contains each account element and its description. For information about storing credentials, see Section 5.5, Adding and Maintaining Credentials for Use With the Action Framework .

5.3.5 Policies

The policy element is used to describe the location of OWSM client policy files used in accessing secured Web Services as action targets. Each policy element provides a name to reference the policy that may then be used by service-access elements as a shorthand to specify that the AES should apply the policy file referred to when invoking an action target covered by that service-access element. The following example is a policy entry. Table 5–7, Policy Elements and Descriptions describes each element. policy nameSAMLPolicyname policyfileActionsSAMLPolicy.xmlpolicyfile policy

5.3.5.1 Policy Elements Descriptions

Table 5–7, Policy Elements and Descriptions contains each policy element and its description. Table 5–6 Account Elements and Descriptions Element Description name This element specifies the name referenced in registry service-access elements, or the appserver element for Java registries. Each account must have a unique name within the Action Framework configuration. description This element is reserved for future use. adminonly This element is reserved for future use. You must set this element to false. credentialkey This element is used for looking up credentials in Oracle’s Credential Store Framework CSF. A set of credentials with the specified key must exist in the domain credential store. credentialmap This element specifies the map in which to look for the credentialkey in CSF. Note: To invoke a secured Web service as described above, you must configure OWSM to work with Actions. For more information, see Section 5.5.3, Configuring Oracle Web Services Manager .