2Setup and Configuration

This chapter contains the following:

Mapping to Work Areas

You can find the Reports and Analytics panel tab in many work areas, and the analytics and reports you see in it depend on the work area. You can define what's available for a specific work area, by mapping reports from the business intelligence (BI) catalog to that work area. In this mapping context, reports refer to both analytics and reports. Your changes apply to all users who have access to the work area you're mapping.

Mapping Reports from Your Work Area

To map reports to the work area that you're in:

  1. Expand the Reports and Analytics panel tab.

  2. Click the Edit Settings icon in the panel tab.

    You see all the reports that are currently mapped to your work area.

  3. Click Select and Add.

  4. Find the report in the catalog and select it.

  5. Click OK.

  6. To remove any mapping, select the report and click Remove.

  7. Save your work.

Mapping Reports to Any Work Area

To map reports to any work area that you have access to:

  1. In the Setup and Maintenance work area use the Map Reports to Work Areas task.

  2. Select the application of the work area you want to map to.

  3. Select the work area.

  4. Click Search and see all the reports that are currently mapped to that work area.

  5. Click Select and Add.

  6. Find the report in the catalog and select it.

  7. Click OK.

  8. To remove any mapping, select the report and click Remove.

    Tip: Click Synchronize to remove all mappings to any reports that are no longer in the catalog. You synchronize all work areas, not just the one you're mapping.
  9. Save your work.

Either no reports are currently mapped to the work area you select on the Map Reports to Work Areas page, or you don't have access to the reports that are mapped.

Similarly, when you're selecting a report to map, you can see only the reports that you have access to. Ask your administrator to either:

  • Assign you roles that have access to the reports you want to map to work areas.

  • Grant the Reports and Analytics Region Administration Duty to someone who already has access to those reports.

In the Edit Settings window, you might not see a currently mapped report because you don't have access to it.

Similarly, when you're selecting a report to map, you can see only the reports that you have access to. Ask your administrator to either:

  • Assign you roles that have access to the reports you want to map to work areas.

  • Grant the Reports and Analytics Region Administration Duty to someone who already has access to those reports.

Setting Up Currency

Setting Currency Preferences for Analytics

Oracle Transactional Business Intelligence gives you the ability to set your personal currency preferences, as well as set currency preferences which determine how your analyses display currency and calculate exchange rates.

The user preferences for your cloud offering are set in the cloud environment, and the currency preferences for analyses are set in Oracle Business Intelligence (BI). Both user preferences impact how your report currency is calculated and displayed. Your application administrator sets the corporate currency as the common currency basis for all users.

There are three ways currency is set in cloud and BI environments:

  • User Currency - Set by the business user in Regional settings. This setting applies to the entire application interface for that user only. The currency options available are set by your application administrator.

  • Reports Currency - Set by the business user in BI in My Account settings in the Reports area. The setting applies to that user only and only relevant for report production.

  • Corporate Currency - Set by the application administrator. This setting applies to all users in that company.

Setting Your General User Currency

User currency settings govern the currency that is used as the default for your application interface. User currency is set in the application and applies to your entire interface for your signed-in session.

To set your user currency:

  1. Navigate to Tools, Set Preferences.

  2. Select General Preferences > Regional.

  3. Select the preferred currency to be used. Available currencies include those set up for your company by your application administrator.

Setting Your Personal Analysis Currency

The analysis currency determines the currency that is used in reports and analyses. It also determines how and when your currency conversion rates are calculated.

To set your currency for reports and analyses:

  1. Navigate to Business Intelligence.

  2. Click Analytics in the navigator menu.

  3. Click Browse Catalog.

  4. Click your user name and and select My Account.

  5. Go to the Preference.

  6. Select your choice in Currency.

The following table describes the currency menu options.

Currency Name Description

Entered Currency

Currency used on a transaction.

<Application> Currency

Currency set up in each respective Cloud application as the common Corporate currency used company-wide.

User Preferred Currency using Simple Currency Management

Conversion to User Preferred Currency is performed at the time your run the report, and is calculated from the Corporate currency based on the last time the record was updated and saved or closed.

User Preferred Currency using Advanced Currency Management

Conversion to User Preferred Currency happens on the date your run the report, and uses the currency indicated on the record.

Setting a Default Currency Conversion Option for All Users

The default setting for the way currency conversion is handled for analytics is the User Preferred Currency Using Simple Currency Management. This simple currency management setting provides the best run-time performance when dealing with currency exchange rate management. But there are cases when your organization might want to standardize the setting for all system users, by setting the default preference to another option, such as CRM Currency or User Preferred Currency Using Advanced Currency Management.

To change the default currency setting for all users, administrators need to add a profile option and a corresponding value. Note that when administrators change the default currency setting for users in their organization, individual users can still override that setting and select their preferred currency in My Account.

The following table shows the profile option code parameters to override the default currency setting.

Profile Code Profile Value Description

BI_DEFAULT_CURRENCY_CONVERSION_METHOD

CRM Currency - Defaults to Application Currency.

BI_DEFAULT_CURRENCY_CONVERSION_METHOD

User Preferred Currency 1 - Defaults to User Preferred Currency Simple Currency Management.

BI_DEFAULT_CURRENCY_CONVERSION_METHOD

User Preferred Currency 2 - Defaults to User Preferred Currency Advanced Currency Management.

Adding a Currency Profile

To set default global currency conversion types for all users, administrators create a currency profile using the Manage Profile Options task in the Setup and Maintenance work area. Only administrators can change global currency preferences by creating profiles.

To add a currency profile:

  1. In the Setup and Maintenance work area, go to the Manage Profile Options task.

  2. Enter the following values:

    • Profile Option Code : BI_DEFAULT_CURRENCY_CONVERSION_METHOD

    • Profile Display Name : BI Default Currency Conversion Method

    • Application

    • Module

    • Start Date : Provide previous day's date to proceed to next step to define values.

  3. Click Save and Close.

  4. In the Manage Profile Options dialog box, you see your new profile. Check the Enabled box for Site.

  5. Click Save and Close.

Defining Currency Profile Values

Once you have created your currency profile, the last step is to define the profile value. This step defines which currency management option is assigned to that profile.

To define a currency profile value:

  1. In the Setup and Maintenance work area, use the Manage Administrator Profile Values task.

  2. In Profile Option Code search for your profile: BI_DEFAULT_CURRENCY_CONVERSION_METHOD.

  3. In Manage Administrator Profile Values, Click + (Add icon) .

  4. Select Site as the Profile level.

  5. Enter "User Preferred Currency 2" in Profile Value.

  6. Click Save and Close to close the dialog.

User-Preferred Currency Reporting and Exchange Rates

The simple and advanced user-preferred currency choices determine how and when your currency exchange rates are calculated for your reports. For both simple and advanced currency management, when you save or close a report, the application sets the exchange rate at that time. The option you choose impacts how quickly your reports are generated at run time. Each case includes trade-offs, as detailed in the examples.

User Preferred Currency using Simple Currency Management

The advantage of this option is performance - the application doesn't have to look up the rate for each transaction because when you close or save a record, the application converts it to your corporate currency at that day's rate. When you run the opportunity report, the application multiplies that value by your preferred currency exchange rate for the date you run the report. This eliminates the need for the application to cycle through each record, and calculate the corresponding exchange rate to your preferred exchange rate at the time that record was closed or last saved. It simply takes the value on record for the original transaction exchange to corporate currency, and multiplies it by your preferred currency exchange rate at the time your run the report.

As an example of user preferred currency using simple currency management, a user updates and saves or closes an opportunity record with associated revenue of one million Indian Rupees on January 31st with an exchange rate of 0.01403 Rupees to one US Dollar. The user then runs an opportunity report in US Dollars on March 31st. In the report, the US Dollar Corporate Currency is set at the January 31st rate it was saved at, in this case reporting as $14,030, or one million multiplied by 0.01403. Finally, an opportunity report on March 31st in Euros uses the March 31st conversion rate for US Dollars to Euros of 0.75017 to convert the recorded US Dollar amount into Euros, in this example one million multiplied by 0.1403, which is the January 31st Rupee to US Dollar exchange rate, multiplied by 0.75013, which is the March 31st rate for Euros. This requires less processing, because the January 31st Rupee to US Dollar exchange rate, while not exact on March 31st, is used as the basis for the calculation of the March 31st opportunity revenue conversion to Euros at the later exchange rate.

The following figure describes an example of user preferred currency using simple currency management.

User preferred currency using simple currency management.

User Preferred Currency using Advanced Currency Management

This option provides a more precise exchange rate, since it goes through each record to determine the rate on the date the record was updated or closed. The downside of this option is performance. Your reports will take longer to run. The application has to cycle through each record and match currency exchange rates to the date the record was closed or updated and saved.

As an example of user preferred currency using advanced currency management, a user updates and saves or closes an opportunity record with associated revenue of one million Indian Rupees on January 31st, when an exchange rate of 0.01050 Rupees to one Euro applies. The user then runs an opportunity report on March 31st. In the report, the User Preferred Currency of Euros is applied, using the March 31st Rupee to Euro rate of 0.01052, requiring calculation during report processing to resolve the opportunity to 10,520 Euros. Finally, an opportunity report on March 31st in Euros again uses the March 31st conversion rate for Euros.

The following figure describes an example of user preferred currency using advanced currency management.

User Preferred Currency using advanced currency
management.

Why do I see amounts of zero in analyses?

The currency exchange rates might not be set up correctly. For example, you choose EUR as your preferred currency in general preferences, and your corporate currency is USD. Amounts in analyses are displayed in EUR after conversion from USD, based on the current exchange rate. But if the exchange rate between EUR and USD isn't set up, or if the conversion fails for any reason, then the amounts show as zero. If this happens, contact your help desk.

Configuring Business Intelligence Publisher

Managing Report Delivery Servers: Overview

Oracle Business Intelligence Publisher, the report generation and delivery engine, requires configuration and tuning to deliver reports to users.

Report requests are received by Publisher from:

  • Oracle Enterprise Scheduler

  • The Reports and Analytics work area and panel tab

  • Application pages

Requests submitted through Oracle Enterprise Scheduler are processed by the Oracle BI Publisher scheduler. Requests submitted through the Reports and Analytics work area or panel tab can be either real-time online requests or scheduled requests. Requests submitted through an application may call Oracle Enterprise Scheduler or may return report request results directly back to the application page.

Oracle BI Publisher is configured to accept requests from Oracle Applications Cloud. However, before you can deliver report documents to their destinations, you must define the delivery servers in Oracle BI Publisher. Use the Oracle BI Publisher Administration page to define your delivery servers.

Once delivery servers are defined, you can further configure the number of report processor and delivery threads to best handle your processing and delivery requirements. In addition, you can configure report properties for the delivery servers or at the report level to tune performance of your reports. To diagnose report processing issues, BI Publisher provides a set of scheduler diagnostics.

Navigating to the Oracle BI Publisher Administration Page: Procedure

You use the Oracle BI Publisher Administration Page to perform most tasks related to report delivery and performance.

Use the Oracle BI Publisher Administration page to:

  • Configure delivery servers

  • Manage report and delivery processors

  • View scheduler diagnostics

  • Set system properties and report runtime configuration properties

Request the Oracle Applications Cloud security administrator to assign the BI Platform Administrator duty role (BI stripe) to the person responsible for administering BI analyses, dashboards, and BI Publisher reports. Administration tasks include security permissions for objects, organizing objects into folders, accessing log files, and several other tasks.

Navigating to the Administration Page

To navigate to the Oracle BI Publisher Administration page:

  1. Click Tools > Reports and Analytics in the Navigator.

  2. In the Reports and Analytics work area, click Browse Catalog.

  3. In the Catalog page, click Administration, then click Manage BI Publisher.

Configuring Report Delivery Servers: Procedure

Set up the report delivery servers to support printing.

Configuring Servers

To configure delivery servers:

  1. From the BI Publisher Administration page, click Delivery Configuration.

  2. Enter values in the Delivery Configuration Options tab to set general properties for email deliveries and notifications.

  3. To configure a delivery server, click the appropriate tab.

Understanding the Report and Delivery Processors: Overview

When Oracle Enterprise Scheduler initiates a job, it is picked up by the BI Publisher scheduler queue.

  • Job Processor: Listens for requests from the scheduler queue. When the job information is received, the job processor executes the data model (and splits the data for bursting jobs), stores the data in the shared temporary folder, and sends the report metadata to the report queue.

  • Report Processor: Listens for requests from the report queue. When the report information is received, the report processor generates the report documents, stores it in the shared temporary folder and puts the delivery information in the delivery queue.

  • Delivery Processor: Listens to the delivery queue and handles the delivery of reports for its channel. The delivery processors are:

    • Email Processor

    • File Processor

    • FTP Processor

    • Print Processor

    • WebDAV Processor

    • Fax Processor

Managing Report Processing and Delivery Server Load: Procedure

Manage the processors in the BI Publisher Scheduler Configuration page.

Managing Processing and Server Load

By default, each processor is enabled and the thread count for each is set to five. For each managed server that is running in the BI cluster, a table for that instance's processors is displayed. Use the table to enable or disable processors for the instance and configure the thread counts.

To configure processor threads:

  1. From the BI Publisher Administration page, click Scheduler Configuration.

  2. In the Cluster Instances region of the Scheduler Configuration page, enter the Number Threads value in the processor configuration table.

  3. All processors are automatically set to use the number of threads defined in the Threads Per JMS Processor value of the JMS Configuration region of the page. Enter a value in the Number Threads column to change the value from this default.

After performing the scale-out procedure, configure the processor threads for each cluster instance using the same steps.

Diagnosing Report Processing Issues: Procedure

The Scheduler Diagnostics page provides the runtime status of the scheduler. Among others, it provides status of its JMS configuration, JMS queues, cluster instances, scheduler Database, and Oracle Enterprise Scheduler.

Diagnosing Issues

To access the Scheduler Diagnostics page:

  1. Navigate to the Oracle Business Intelligence Publisher Administration page.

  2. In the System Maintenance group, click Scheduler Diagnostics.

Configuring System Properties for Reports: Procedure

Use the Oracle BI Publisher Runtime Configuration page to set the system-level runtime properties for reports.

Configuring Reporting Properties

To access the Runtime Configuration page:

  1. Navigate to the Oracle Business Intelligence Publisher Administration page.

  2. In the Runtime Configuration group, click Properties.

Changing Memory Guard Settings: Procedure

Memory Guard settings for Oracle BI Publisher have default settings optimized for performance. To change Memory Guard settings from the defaults, log a service request with details in the Memory Guard request template.

Reviewing Memory Guard Settings

To Review Memory Guard Settings:

  1. Click Properties.

  2. Click Manage BI Publisher.

  3. In the Runtime Configuration, click Properties.

  4. The Memory Guard settings set thresholds for report size and runtimes.

Changing Memory Guard Settings

To change the Memory Guard settings, review the process described in MyOracle Support (Doc ID 2199494.1). Use the provided Customer Memory Guard Change Request Template to provide details of the changes you want and attach it to a service request for review by Oracle Support.

Using a Dedicated Business Intelligence Publisher Cluster for Critical Jobs: Procedure

For some time-sensitive reports, including for example paycheck and invoice generation, you can use a dedicated Business Intelligence Publisher cluster by setting the report's priority as critical, ensuring that reports are run during critical time windows.

Critical jobs are assigned to a dedicated cluster. To set a report as critical:

  1. Open the report.

  2. Click Properties.

  3. In the Advanced Report Properties in the General tab, select Critical in the Job Priority list.

Determining Which Reports Are Prioritized as Critical

To review which reports have been marked as critical, navigate to Report Job Histories, where critical jobs are highlighted.

Download Armored PGP Public Key Files: Procedure

To support encrypted communication channel from the BI Publisher Server to an FTP site, you download a Pretty Good Privacy (PGP) public key file in ASCII armor format and configure your FTP server to use PGP encrypted files in that format.

Download PGP Public File

Download PGP keys in the BI Publisher Administration page.

To download a PGP key in armored format:

  1. Navigate to the BI Publisher Administration page.

  2. In the Security Center section, click the PGP Keys link to open the PGP Keys page.

  3. In the PGP Keys section, click the Download BI Publisher Key [name] (ASCII armored) Download icon.

  4. In the Opening bipublisher@oracle.com.key dialog box, click OK. Enter a name for the key or accept the default in the Save dialog box and click OK.

PGP Encryption for FTP Delivery: Upload and Apply PGP Keys

To secure report delivery through the FTP/SFTP channel, you can encrypt the report using PGP Encryption.

Upload PGP Keys

You upload, test, and delete PGP keys in the BI Publisher Administration page.

To upload PGP keys:

  1. Navigate to the BI Publisher Administration page.

  2. In the Security Center section, click the PGP Keys link to open the PGP Keys page.

  3. In the PGP Keys section, click Browse and select the PGP key file in the Open dialog box.

  4. Click OK.

  5. Click Upload. After the file is uploaded, it is imported into the keystore and its details are visible in the PGP Keys table. If a key with the same ID is imported again, the file is overwritten.

  6. Click the Download icon of the key in the Encrypted Test Output column of the PGP Keys table to download and decrypt a test output file using the secret key of the imported public key. Successful decryption confirms the encryption is working for your keys.

Delete a PGP Key

To delete an imported public key, click the Delete icon.

Apply PGP Encryption to FTP Delivery Channel

To create an FTP channel:

  1. Navigate to the BI Publisher Administration page.

  2. In the Delivery section, click the FTP link to open the FTP page.

  3. Add a new FTP Server, using the user name and the password and private key password set when you created the PGP key. The Filter Command field is read-only and is updated automatically when you select a PGP key.

  4. Click Test Connection.

  5. Select the PGP Key ID of the key you uploaded from the list.

  6. If you want PGP encrypted output in ASCII armored format on the destination FTP server, select the ASCII Armored Output check box. The Filter Command is updated with a -a option.

  7. Select the true check box for Sign Output to sign the encrypted document. If you select this check box, a -s parameter is added to the existing filter command.

  8. Test the connection again to confirm that an encrypted test file is sent to the remote directory. The FTP delivery channel can now be used in a scheduled job.

Configure the Email Addresses for Notifications

Use the Delivery Configuration Options page to set e-mail addresses for notifications from BI Publisher.

To configure the email address for delivery notification:

  1. Log in as an administrator.

  2. In the BI Publisher home page, click Administration, and then click the Delivery Configurationtab.

  3. Enter the email addresses in the Email From Address and Delivery Notification Email From Address fields.

  4. Enter the email subject text in the following fields:

    • Success Notification Subject

    • Warning Notification Subject

    • Failure Notification Subject

    • Skipped Notification Subject

Set Up Auditing: Procedure

BI Publisher logs statistics about user activity using that can be reported on in reports. An administrator

Logged User Events

Important report publishing events are logged in the audit database, including the following. You can control the level of auditing.

  • Tracks the start and end time of request events for reports (normal and scheduled).

  • Tracks the relationship between requested start time, report execution events (data processing, bursting, rendering, and delivery), and request end events for report requests

Access Audit Records

To access audit records:

  1. Configure the AuditDB data source.

    1. Click Administration.

    2. Click the JNDI Connection.

    3. Click Add Data Source, and enter:

      • Data Source Name: AuditDB

      • JNDI Name: jdbc/AuditViewDataSource

    4. Click Test Connection to confirm the connection.

    5. Click Apply.

  2. Create a data model.

    1. In the Home page, click New and select Data Model.

    2. Click New Data Set and select SQL Query.

    3. In the Edit Data Set dialog box, select AuditDB in the Data Source list.

    4. Accept the default, Standard SQL, in the Type of SQL list.

    5. Enter the following SQL statement:

      SELECT IAU_TSTZORIGINATING, IAU_INITIATOR, IAU_EVENTTYPE, IAU_RESOURCE from BIPUBLISHER_V 
      ORDER BY IAU_TSTZORIGINATING DESC
    6. Click OK.

    7. Click Save to save the data model.

    8. Click View Data.

    9. In the Data tab, click View.

    10. Click Save As Sample Data.

    11. Click Save to save the data model.

    12. Click Create Report.

  3. Create a simple report with table layout.

Configuring Deep Links

Registering Business Intelligence to Support Deep Linking: Procedure

Deep links in analyses allow you to navigate from analytics to specific attributes and objects in your transactional pages so that you can work with them directly. To support deep links, use the Setup and Maintenance work area to register the Business Intelligence Server as a third-party application.

Registering Business Intelligence Server as a Third-Party Application

To register the BI Server:

  1. Use the Manage Third Party Applications task.

  2. Click Create.

  3. Enter AnalyticsApp as the application name.

  4. Enter the full URL for the BI Server (for example: http://host:port/analytics/saw.dll).

  5. Enter Analytics Server as the Partner Name.

  6. Click Save and Close.

Creating Deep Links in Analyses: Procedure

Create deep links in analyses to navigate from analytics to specific attributes and objects in your transactional pages to work with them directly.

To create deep links in an analysis:

  1. In the Reports and Analytics work area, click Browse Catalog.

  2. Create or edit an analysis. Use a subject area that includes the attribute you want to link to in the transactional pages, and ensure that you include the object ID.

  3. On the Criteria tab, click the Options icon for the attribute column on which you need a deep link and select Column Properties.

  4. Open the Interaction tab in the Column Properties dialog box.

  5. In the Primary Interaction list in the Value section, select Action Links to display the Action Links table.

  6. Select the Do not display in a pop-up if only one action link is available at runtime option.

  7. Click Add Action Link.

  8. In the New Action Link dialog box, enter the link text for the navigation.

  9. Click the Create New Action icon and select Navigate to a Web Page.

  10. In the Create New Action dialog box, enter the URL to navigate to, which references parameters you define in the prompt. For shared analyses://<hostname>/fscmUI/faces/deeplink?objType=@{1}&objKey=<object ID>=@{2}&action=@{3}&returnApp=AnalyticsApp&returnAppParams=PortalGo%26path=</shared/Custom/<folder>/@{6}

    For personal analyses stored in My Folders: //<hostname>/fscmUI/faces/deeplink?objType=@{1}&objKey=<object ID>=@{2}&action=@{3}&returnApp=AnalyticsApp&returnAppParams=PortalGo%26pather=/users/@{5}/@{6}

  11. Click Define Parameters to add corresponding parameters for the URL.

  12. In the Define Parameters section, click Add Parameter to add the following mandatory parameters:

    Name Prompt Type of Value Value Fixed Hidden Notes

    1

    Object Type

    Value

    <Object Type>

    Selected

    Selected

    Used for shared and personal analyses.

    2

    <Prompt Name>

    Column Value

    Column Name in "<table.name>"."<column.name>" format

    Selected

    Selected

    Used for shared and personal analyses.

    3

    Action

    Value

    edit

    Selected

    Selected

    Used for shared and personal analyses.

    4

    returnApp

    Value

    AnalyticsApp

    Selected

    Selected

    Used for shared and personal analyses.

    5

    Logged in User

    Session Variable

    USER

    Selected

    Selected

    Session variable parameter used for personal analysis permissions.

    6

    Report Name

    Value

    Analysis Name

    Selected

    Selected

    Used for shared and personal analyses. The name of the analysis to return to after working in the transactional page.

  13. Click Options to set how the page opens.

  14. In the Action Options dialog box, select Open in New Window to open the page in a new window.

  15. Save your work.

  16. If you have provided the Return Application name, a Return icon is available in the transactional page to return to the analysis.

Setting Up the Delivery Channel

Setting Up the Delivery Channel and Enabling Encryption: Procedure

BI Publisher supports Oracle WebCenter Content as the recommend delivery channel for delivering reports for distribution. You can use the provisioned connection to deliver files from BI Publisher to WebCenter Content, or configure a custom connection to deliver Pretty Good Privacy (PGP) encrypted files from BI Publisher.

Using the Default Connection

By default, a provisioned WebCenter Content connection, FA_UCM_Provisioned, uses a provisioned FUSION_APPS_OBIA_BIEE_APPID user to connect to WebCenter Content with security groups and accounts to support the most common use cases.

Creating a Custom Connection

If you have specific requirement to access WebCenter Content using user credentials other than FUSION_APPS_OBIA_BIEE_APPID, or if you want to use PGP key encryption, you can add a custom connection.

When you create a custom connection for WebCenter Content, it must use the same Uniform Resource Identifier (URI) as the provisioned connection, but should have its own user name and password.

To create a custom connection:

  1. In the BI Publisher Administration page, navigate to the Content Server tab in the Delivery section, and click Add Server.

  2. Enter the same URI used by the provisionedFA_UCM_Provisioned WebCenter Content server.

  3. Enter the server name, URI, user name, and password.

  4. Leave Enable Custom Metadata deselected. Custom metadata is not used.

  5. Click Test Connection to ensure that you can connect.

  6. Click Apply.

Configuring File Encryption

You can use PGP encryption to secure the file delivery.

To use PGP encryption:

  1. Upload the PGP public keys to import the PGP keys of WebCenter Content.

    1. Navigate to the Security Center section in the BI Publisher Administration page.

    2. Click PGP Keys to open the PGP Keys page.

    3. In the PGP Keys section, click Browse and select the PGP key file in the Open dialog box.

    4. Click Upload. The uploaded file is imported into the keystore and its details are visible in the PGP Keys table. If a key with the same ID is imported again, the file is overwritten.

    5. Click Download for the key in the Encrypted Test Output column of the PGP Keys table to download and decrypt a test output file using the secret key of the imported public key. Successful decryption confirms the encryption is working for your keys.

  2. Enable delivery of PGP encrypted files in a custom connection to WebCenter Content.

    1. Navigate to the Delivery section and the Content Server page.

    2. Select the custom content server connection you want to configure.

    3. Select the imported key by its ID from the PGP Keys list and verify that the GPG command is populated in the Filter Command.

    4. Click Apply.

Delivering Content: Procedure

Use a scheduled job to deliver content and documents.

Scheduling a Job to Deliver Content

To schedule a job to deliver documents:

  1. In BI Publisher, click Create and select Report Job.

  2. In Schedule Report Job, on the General tab, click search for the Report field.

  3. In the Open dialog box, navigate to and select the report, and then click Open.

  4. In Schedule Report Job, in the Frequency list on the Schedule tab, select the option to use for this report.

  5. In Schedule Report Job, on the Output tab, choose Content Server in the Destination Type list.

  6. Click Add Destination.

  7. Select the server from the Server list.

  8. Select the WebCenter Content security group to assign to the report.

  9. (Optional) Select an account within the Security Group to assign to the report.

  10. (Optional) Select the Folder Path to deliver files to an existing folder in the content server.

  11. (Optional) Enter a value for Author. If you don't enter an author, your user name is used for the Author metadata in WebCenter Content.

  12. (Optional) Type a Title for the report. If you don't enter a title, the layout name is used for the title.

  13. Enter the file name to assign to the delivered document on the remote server, for example, myreport.pdf.

  14. Ensure that you don't include files with the same name in one folder. The File Name field is used as the Native File Name in WebCenter Content. If you don't supply a file name value, the Output name is used.

  15. (Optional) Type a description to include with the document in WebCenter Content.

  16. Deselect Include Custom Metadata.

  17. Click Submit.

  18. In the Submit dialog box, type a name in the Report Job Name field, and click OK.

  19. Click Home and navigate to the Report Job History page to verify the report delivery status.