5-8 Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition
5.3.2.4 Registry Elements Descriptions
Table 5–4, Registry Entry Elements and Descriptions contains each registry element
and its description.
Table 5–4 Registry Entry Elements and Descriptions
Element Description
registry This element is the outer-most element that contains the registry definition.
id This element holds an internal identifier that must be unique for each registry.
name This element is the display name that is used by the ActionRegistryService when
displaying the list of registries. The name that you specify in this element is also used as the root path for any targets within this registry.
content-type You can use Oracle supplied values only. This element points to a content-type,
which is another element defined in the Action Framework configuration file. For more information, see
Section 5.3.3, Content Types .
provider-class You can use Oracle-supplied values, only.
Table 5–5, Provider-Class Element Values
contains the valid values for this element. description
This element is reserved for future use. location
This element specifies the path to the registry that may contain aliased elements. For example, a WSIL file.
service-access This element is optional. You can define zero or more service-access elements in a
registry definition. The service-access element specifies the authentication required to access the registry
and, where specified, sub-paths within that registry. Note the following:
■
If a registry element does not have any service-access elements, no authentication is used when accessing services from that registry.
■
The service-access elements that specify a path element apply the account element only to services found under the specified path within the registry.
■
If a registry element contains a service-access element with just an account element that points to an account defined in the accounts element, then that
account is used to access all services within that registry that are not specified by specific path-based service-access elements.
path This element is optional. This element is located within the service-access element
and specifies a path to a subset of the services in the registry. The path is not a physical location. The path hierarchy starts with the registry name and can be found
in the user interface by expanding the nodes that lead to a particular action target when creating a new action.
account This element is optional. This element is located within the service-access element
and points to an instance of an account element defined elsewhere in the configuration file.
If a registry element contains a service-access element with just an account element, then that account is used to access all services within that registry that are not
specified by specific path-based service-access elements. For webservices registries, the credentials held against the account referenced are
used by the Action Framework to invoke target actions if the propagateIdentity element has a value of false.
For epm registries, the credentials held against the account are used by the Action Framework to browse for EPM content.
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
Kategori