Changing the Reporting and Analytics Published Site URL

These instructions provide a high-level overview and basic guidance to the areas within the Oracle WebLogic console that apply to this task. The Oracle WebLogic Server documentation contains detailed information and instructions for understanding and performing configurations within the Oracle WebLogic console.

1. In the Oracle WebLogic console, navigate to the Summary of Servers page, click the application server name (typically appServnumber), click Configuration, click Federation Services, click SAML 2.0 General, and then change the Published Site URL.

   The Published Site URL is case sensitive in server cluster deployments.

2. Publish the metadata to the following location:INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\app_metadata.xml

   In a two-box or cluster installation, the WebLogic console creates the metadata file on the Reporting and Analytics application server. You must copy the file to the OBI server running the Oracle WebLogic Administration Server.

3. Navigate to Security Realms, click myrealm, click Providers, click Authentication, click the saml2AP identity assertion provider, and then click Management.
   1. Delete and then re-create the app_data service provider partner.
   2. Use the metadata file you created for the new published site URL.
   3. Select Enabled, enter /analytics/* in the Redirect URIs field, and then select Only Accept Signed Artifact Requests.
4. Change the value for portalDomainURL in microsConfig.properties.
5. If you are not changing the OBIEE published URL, redeploy portal.ear. Re-Deploying Reporting and Analytics Applications contains instructions for redeploying applications.