Set Up Delivery Destinations
This topic describes the setup required to deliver reports. It also describes how to set up the HTTP notification server.
Note:
The email, FTP, printer, fax, and content management hosts must be accessible from the public internet.Configure Delivery Options
You can define the SSL certicate file and set the general properties for e-mail deliveries and notifications.
If Publisher encounters an issue connecting to the email server, it attempts to send the email again for three times, with a 30-second interval between each attempt.
Understand Printer and Fax Server Configuration
Understand your printer type before you set up the printer or fax server.
Regardless of the operating system, the printer destination can be any IPP server. The IPP server can be the printer itself, but if the printer doesn't natively support IPP, you can set up a print server that does support IPP (such as CUPS), and then connect to the print server to the printer.
To send a fax, you must set up Common Unix Printing Service (CUPS) and the fax4CUPS extension. For information on setting up CUPS or Windows IPP print servers and how to connect network printers to them, refer to the CUPS or Windows IPP software vendor documentation.
PDF is a popular output format for business reports. However, some reports require printing directly from the report server. For example, paychecks and invoices are usually printed as scheduled batch jobs. Some printers with PostScript Level 3 compliant Raster Image Processing can natively support PDF documents, but there're still many printers in business use that only support PostScript Level 2 that can't print PDF documents directly.
To print PDF documents directly, if your printer or print server doesn't support printing PDF:
-
Select a filter - PDF to PostScript or PDF to PCL.
-
Configure a custom, or third-party filter.
A filter enables you to call a conversion utility to convert the PDF to a file format supported by your specific printer type. You can use the PDF to PCL conversion only for font selection requirements for check printing. For generic printing requirements, use the PDF to PostScript level 2 filter.
Selection of PDF to PCL filter automatically populates the Filter Command field. You can embed PCL commands into RTF templates to invoke the PCL commands at a specific position on the PCL page; for example, to use a font installed on the printer for routing and account numbers on a check.
You can also call a custom filter using operating system commands.
To specify a custom filter, pass the native OS command string with the two placeholders for the input and output filename, {infile} and {outfile}.
This is useful especially if you're trying to call IPP printers directly or IPP printers on Microsoft Internet Information Service (IIS). Unlike CUPS, those print servers don't translate the print file to a format the printer can understand. With the filter functionality, you can call any of the native OS commands to transform the document to the format that the target printer can understand.
For example, to transform a PDF document to a PostScript format, enter the following PDF to PS command in the Filter Command field:
pdftops {infile} {outfile}
To call an HP LaserJet printer setup on a Microsoft IIS from Linux, you can set Ghostscript as a filter to transform the PDF document into the format that the HP LaserJet can understand. To do this, enter the following Ghostscript command in the Filter Command field:
gs -q -dNOPAUSE -dBATCH -sDEVICE=laserjet -sOutputFile={outfile} {infile}
For fax servers, you can use the filter to transform the file to Tag Image File Format (TIFF).
Add a Printer
You can set up a printer to print reports.
The printer server must be accessible from the public internet.
Add a Fax Server
You must set up Common Unix Printing Service (CUPS) and the fax4CUPS extension, if you want to send fax.
The fax server must be accessible from the public internet.
- From the Administration page, under Delivery, select Fax, and then click Add Server.
- Enter the server name and the URI (Uniform Resource Identifier) of the fax server.
- Optional: If your fax server doesn't support printing PDF, enter a filter to call a conversion utility to convert the PDF to a file format supported by your specific fax server.
- Optional: Enter the user name, password, authentication type (None, Basic, Digest), and encryption Type (None, SSL) of the fax server.
- Optional: Enter the host, port, user name, password, and authentication type (None, Basic, Digest) of the proxy server.
- Optional: In the Access Control section, deselect Public.
- From the Available Roles list, select one or more roles you want to provide access to the delivery channel, and click Move to add them to the Allowed Roles list.
- Click Apply.
Add an Email Server
You can add an email server to deliver reports by email.
The mail server must be accessible from the public internet.
Deliver Reports Using Email Delivery Service on Oracle Cloud Infrastructure
You can use the Email Delivery service on Oracle Cloud Infrastructure to deliver reports.
If you don't have access to Oracle Cloud Infrastructure Console, ask your Oracle Cloud Infrastructure administrator to provide you access.
Add an HTTP or HTTPS Server
The administrator can add an HTTP or HTTPS sever to send a notification request to after the report completes.
You can register an application URL or postprocess HTTP or HTTPS URL as an HTTP server.
The HTTP notification sent by Publisher posts a form data for Job ID, report URL and Job Status to the HTTP Server URL page.
- From the Administration page, under Delivery, select HTTP, and then click Add Server.
- Enter the server name and the URL of the server.
- Optional: Enter the host, port, user name, password, authentication type (None, Basic, Digest), and and encryption type (None, SSL) of the server.
- Optional: If the notification is to be sent through a proxy server, enter the user name, password,and the authentication type (None, Basic, Digest).
- In the Access Control section, deselect Public.
- From the Available Roles list, select one or more roles you want to provide access to the delivery channel, and click Move to add them to the Allowed Roles list.
- Click Apply.
Add an FTP or SFTP Server
You can add an FTP server or SFTP server as a delivery channel for Publisher.
If the destination file name supplied to the scheduler contains non-ascii characters, UTF-8 encoding is used to specify the file name to the destination FTP server. Your FTP server must support UTF-8 encoding or the job delivery will fail with "Delivery Failed" error message.
The FTP server or SFTP server must be accessible from the public internet.
Publisher doesn't support FTP over TLS / SSL (FTPS). You can't use FTP over TLS or SSL for delivery. Use SFTP for secure file transfer.
SSH Options For SFTP
Secure File Transfer Protocol (SFTP) is based on the Secure Shell technology (SSH). Publisher supports the following SSH options for SFTP delivery.
Key Exchange Method (Diffie-Hellman) | Server Public Key | Encryption (Cipher Suites) | Message Authentication Code (MAC) |
---|---|---|---|
|
|
|
|
The following algorithms are available only when Publisher is running on a JVM on which the Java Cryptography Extension (JCE) unlimited strength jurisdiction policy files are installed:
- diffie-hellman-group-exchange-sha256
- diffie-hellman-group14-sha256
- diffie-hellman-group16-sha512
- diffie-hellman-group18-sha512
- rsa-sha2-256
- rsa-sha2-512
- aes192-ctr
- aes256-ctr
- hmac-sha2-256
- hmac-sha2-512
Add a Content Server
You can deliver documents to Oracle WebCenter Content.
The content server must be accessible from the public internet.
When you use a content server as a delivery destination:
-
At runtime, the report consumer can tag the report with Security Group and Account metadata (if applicable) to ensure that the appropriate access rights are applied to the document when delivered.
-
For documents that require specific custom metadata fields (such as invoice number, customer name, order date), the report author can map the custom metadata fields defined in Content Profile Rule Sets to data fields in the data model.
Publisher communicates with Oracle WebCenter Content Server using the Remote Intradoc Client (RIDC). The connection protocols therefore follow the standards required by the RIDC. The protocols supported are:
-
Intradoc: The Intradoc protocol communicates to the Content Server over the over the Intradoc socket port (typically 4444). This protocol requires a trusted connection between the client and Content Server and will not perform any password validation. Clients that use this protocol are expected to perform any required authentication themselves before making RIDC calls. The Intradoc communication can also be configured to run over SSL.
-
HTTP and HTTPS: The HTTP protocol connection requires valid user name and password authentication credentials for each request. You supply the credentials to use for requests in the Publisher Administration page.
-
JAX-WS: The JAX-WS protocol is supported only in Oracle WebCenter Content 11g with a properly configured Content Server instance and the RIDC client installed. JAX-WS is not supported outside this environment.
To set up a content server as a delivery destination:
Add an Object Storage
You can use one or more Object Storages to deliver and store reports.
You can configure an Object Storage as a delivery channel, and schedule jobs to deliver reports to the Object Storage.
Make sure you have the permissions to access a compartment in Oracle Cloud Infrastructure Object Storage where you can create a bucket to organize your reports.
Even if you have administrator access to the Object Storage, you should have the permissions to configure the connection and to deliver reports to Object storage. An administrator in your organization must set up the permissions in Oracle Cloud Infrastructure using IAM policies to enable you to deliver files from Publisher to Object Storages. See Getting Started with Policies and Policy Reference.
-
Permissions required for tenancy:
COMPARTMENT_INSPECT
OBJECTSTORAGE_NAMESPACE_READ
-
Permissions required for compartment mangement:
BUCKET_READ
BUCKET_INSPECT
OBJECT_READ OBJECT_OVERWRITE
OBJECT_CREATE
OBJECT_DELETE
OBJECT_INSPECT
Example 6-1 Policy Configuration
Sample policy configuration to allow group g to inspect the compartments in tenancy:
Allow group <g> to inspect compartments in tenancy
Sample policy configuration to allow group g to manage the Object Storage in tenancy:
Allow group <g> to manage objectstorage-namespaces in tenancy
Sample policy configuration to allow group g to manage compartment c and perform the requested operations in the compartment:
Allow group <g> to manage object-family in compartment <c> where any {
request.operation=‘ListBuckets’,
request.operation=‘ListObjects’,
request.operation=‘PutObject’,
request.operation=‘GetObject’,
request.operation=‘CreateMultipartUpload’,
request.operation=‘UploadPart’,
request.operation=‘CommitMultipartUpload’,
request.operation=‘AbortMultipartUpload’,
request.operation=‘ListMultipartUploads’,
request.operation=‘ListMultipartUploadParts’,
request.operation=‘HeadObject’,
request.operation=‘DeleteObject’}
Add a Common UNIX Printing System (CUPS) Server
You add CUPS servers from the Administration page.
You can configure Common Unix Printing Service (CUPS) for sending fax and to enable printing using a printer that doesn’t natively support IPP.
To add a CUPS server:
- From the Administration page, select CUPS to display the list of servers that have been added.
- Select Add Server.
- Enter the Server Name and Host and Port for the CUPS server.
Add an Oracle Content and Experience Server
You can deliver reports to an Oracle Content and Experience server to enable easy access and share reports on the cloud.
- From the Administration page, under Delivery, select Content and Experience, and then click Add Server.
- In the Server Name field, type the name of the server through which you want to deliver the reports to the cloud-based content hub.
- In the URI field, type the URI of the Oracle Content and Experience server. For example, https://host.oraclecloud.com.
- In the Username and Password fields, provide the credentials for accessing the Oracle Content and Experience server.
- In the Access Control section, deselect Public.
- From the Available Roles list, select one or more roles you want to provide access to the delivery channel, and click Move to add them to the Allowed Roles list.
- Click Test Connection.
- Click Apply.