callProcedure Method How to Call the Web Service

4-4 Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition For more information about configuring SAML, see Oracle Fusion Middleware Security and Administrators Guide for Web Services.

4.3.2.4 Assigning the manageRepositories Permission

You must provide the user who will run the Web service with the manageRepositories permission. For information about how to set up security and apply this permission, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.

4.3.2.5 Sample Code

Use the following code to set up client-side security. You can use this code to set up a client-side instances of the Admin Service configured to pass authentication information in a SAML token. This code must reside in an authenticated Web application. The authentication information in the session will be passed automatically to the Web service. You will have to generate client-side proxy classes to use code such as the example code. In this example, the proxies have been generated in the package adminwebservice.client. import adminwebservice.client.; Looks up an instance of the Admin Service and sets the correct authentication information on it. return Admin Proxy to the admin service. protected Admin getAdminService throws Exception { String SERVICE_NAMESPACE = http:ws.admin.obiee.oracle; String SERVICE_NAME = AdminService; String PORT_NAME = AdminPort; String WSS_POLICY_CONFIG_FILE_SAML = wss-policy-saml.xml; URL wsdlURL = new URL http:localhost:7001AdminServiceAdminService?WSDL; QName serviceQname = new QNameSERVICE_NAMESPACE, SERVICE_NAME; QName portQname = new QNameSERVICE_NAMESPACE, PORT_NAME; ServiceDelegateImpl serviceDelegate = new ServiceDelegateImpl wsdlURL, serviceQname, OracleService.class; Admin admin = serviceDelegate.getPort portQname, Admin.class; BindingProvideradmin.getRequestContext.putClientConstants.CLIENT_ CONFIG,toElementthis.getClass.getResourceAsStreamWSS_POLICY_CONFIG_ FILE_SAML; BindingProvideradmin.getRequestContext.putBindingProvider. ENDPOINT_ADDRESS_PROPERTY, getServiceUrl; return admin; } WSS_POLICY_CONFIG_FILE_SAML WSS_POLICY_CONFIG_FILE_SAML is the resource name of a file with the following content: ?xml version=1.0 encoding=UTF-8? Using the Oracle Business Intelligence Metadata Web Service 4-5 oracle-webservice-clients webservice-client port-info policy-references policy-reference uri=oraclewss11_saml_token_with_ message_protection_client_ policycategory=security policy-references port-info webservice-client oracle-webservice-clients

4.4 Using the Oracle BI Server XML Procedures

Oracle BI provides several BI Server XML procedures that you can use to call the Oracle BI Server via JDBC or ODBC. This topic contains detailed information on the following procedures: ■ Extract Project Procedure ■ Modify Metadata Procedure ■ Query Metadata Procedure ■ Query Projects Procedure

4.4.1 Extract Project Procedure

Use the Extract Project procedure to extract a project from the repository. The output results set contains a row for each project defined in the repository. This procedure has the following structure: NQSExtractMetadataProject Input 1.PROJECT_NAMES 2.RPD_NAME optional Output 1.RPD_OBJECT Table 4–3 contains the Extract Project procedure’s input and output parameters and their descriptions.

4.4.2 Modify Metadata Procedure

Use the Modify Metadata procedure to apply changes to the repository. The output result set will contain zero or one row. If the output returns one row, that row will contain error messages. Table 4–3 Extract Projects Procedure Parameters and Descriptions Parameter Description PROJECT_NAMES A delimited list of project names that will be sent to the procedure for extraction. RPD_NAME This parameter is currently not used. It is reserved for future use. RPD_OBJECT Contains a single BLOB object with the binary representation for the extracted repository.