User Interface: Oracle EBS Integration

The following panel and panes are available when you configure an Oracle EBS integration.

Important! For an Oracle EBS integration's print requests to be processed, the integration name in Loftware Enterprise SP must match the integration name specified in Loftware Integration - Oracle EBS by an Oracle administrator. Either the Oracle EBS integration or Loftware Integration - Oracle EBS may be configured first.

Note: If you have upgraded Loftware Enterprise SP from a version prior to Loftware Spectrum 5.0, then any existing Oracle integrations will continue to process print requests. However, most of their properties cannot be edited. Print requests from any new Oracle EBS integrations cannot be processed until Loftware Integration - Oracle EBS has been installed in the Oracle EBS system database. For more information, see Getting Started with Loftware Integration - Oracle EBS.

Menu and Ribbon

The following commands are available from the ribbon in Integrations .

Ribbon Commands

Icon	Command	Description
	New	Create a new object of a specific type.
	Open	Open an existing object.
	Save	Save the displayed object.
	Delete	Delete the displayed object.
	Undo Edits	Reverse the most recent action on an object.
	Redo	Reapply the previously undone action to an object.

File Menu

Command	Description
Close	Close the current object.
Close All	Close all objects that you have open.
Save	Save the object.
Save As	Save a copy of the object under a different name.
Delete	Delete the displayed object.

Home

Button	Command	Description
	Start Integration	Make an integration available.
	Stop Integration	Make an integration unavailable.
	Refresh	Update the displayed data.

View

Button	Command	Description
	Properties	You can configure or view properties when you view any type of integration. For more information, see Properties below.
	Tags	You can categorize an integration by assigning tags to it. For more information about using tags, see Categorize an Integration.
	Service Management	If your Loftware Enterprise SP environment is configured to support distributed services, View > Service Management allows you to configure failover of integration services between Loftware Application Servers. These options are also available in the Service Management page in System . Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information, see High Availability with Distributed Services.

Button

Command

Description

Properties

You can configure or view properties when you view any type of integration. For more information, see Properties below.

Tags

You can categorize an integration by assigning tags to it. For more information about using tags, see Categorize an Integration.

Service Management

If your Loftware Enterprise SP environment is configured to support distributed services, View > Service Management allows you to configure failover of integration services between Loftware Application Servers. These options are also available in the Service Management page in System System Management .

Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information, see High Availability with Distributed Services.

General

The following options are available in the General panel when you configure an Oracle EBS integration.

Note: You must configure each of the options displayed.

Option	Description
Job Target Folder	The unique folder in Loftware Enterprise SP to which status information about print jobs related to this integration should be directed. A different job target folder must be configured for each integration. For more information, see Configure a Job Target Folder.
Default Process	A process to be applied to the integration. Although this field is required, you can select the Generic Document Process in the root folder if you have not configured a custom process that should be applied.
Transaction Size	For a stacked job, the maximum number of labels to allow in a batch. This value is used during job management for packaging print job details into jobs and should be set to be greater than the size of any expected batch of print job details you may need to send. For example, if you have a stacked job with 200 labels to print to the same device, the transaction size should be set to 201 or greater. In this example, a transaction size value of 100 would produce 2 batches which may result in unexpected behavior.
Run As	A Loftware Enterprise SP user account under which requests received from outside of Loftware Enterprise SP are run. This account must have at least the INTEGRATOR role or equivalent permissions and is typically not an interactive user. For more information, see Configuring a Run As User for Integrations. Note: The Loftware Enterprise SP user defined in the Loftware Integration - Oracle EBS properties file should not be used as the Run As user for Oracle EBS integrations.

Advanced

The following options are available in the Advanced panel when you configure an Oracle EBS integration.

Option	Description
Wait for Job Complete	Whether to wait for the job to finish. : The next job may be sent before the current job is complete. This may provide faster performance. (Default) : The next job is not sent until the current job is complete.

Option

Description

Wait for Job Complete

Whether to wait for the job to finish.

: The next job may be sent before the current job is complete. This may provide faster performance. (Default)

: The next job is not sent until the current job is complete.

Archive Options

The following options are available in the Archive Options panel when you configure an Oracle EBS integration.

Option	Description
Archive Original Job File	Whether to save a copy of the original job file in the processed subfolder of the Scan Folder when the job is completed. : The file is not archived. (Default) : The file is saved to the Archive Folder. Note: Selecting this option is recommended only while testing because it generates additional files.
Archive XML	Whether to save a copy of the XML file produced by Loftware Enterprise SP in the processed subfolder of the Scan Folder when the job is completed. : The file is not archived. (Default) : The file is saved to the Archive Folder. Note: Selecting this option is recommended only while testing because it generates additional files.
Archive Folder	A UNC path to a shared folder or a path to a local folder on the Loftware Application Server, such as \\Server01\Archive or C:\Archive. The folder that you specify is created if it does not exist. Using a path to a mapped drive is not recommended. Job files and associated XML files produced by Loftware Enterprise SP can be archived to this folder. Note: This option is displayed only if Archive Original Job File or Archive XML is selected.

Option

Description

Archive Original Job File

Whether to save a copy of the original job file in the processed subfolder of the Scan Folder when the job is completed.

: The file is not archived. (Default)

: The file is saved to the Archive Folder.

Note: Selecting this option is recommended only while testing because it generates additional files.

Archive XML

Whether to save a copy of the XML file produced by Loftware Enterprise SP in the processed subfolder of the Scan Folder when the job is completed.

: The file is not archived. (Default)

: The file is saved to the Archive Folder.

Note: Selecting this option is recommended only while testing because it generates additional files.

Archive Folder

A UNC path to a shared folder or a path to a local folder on the Loftware Application Server, such as \\Server01\Archive or C:\Archive. The folder that you specify is created if it does not exist. Using a path to a mapped drive is not recommended. Job files and associated XML files produced by Loftware Enterprise SP can be archived to this folder.

Note: This option is displayed only if Archive Original Job File or Archive XML is selected.

Properties

The following properties can be configured or viewed by clicking View > Properties when you view any type of integration with Loftware Enterprise™ SP.

Option	Description
Integration Name	A unique name for this connectivity bridge between Loftware Enterprise SP and another application. Required. Characters permitted in names The following characters are permitted in the name: letters, numbers, parentheses, square brackets, ampersands, plus signs, commas, semi-colons, and tildes. Additionally, the following characters are permitted but cannot begin or end the name: spaces, double quotation marks, single quotation marks, hyphens, underscores, periods, and grave accents. For letters, the case that you specify is displayed, but case is ignored when Loftware Enterprise SP interprets a name. If you will be installing the Loftware Enterprise SP application on a computer running Windows Server, and transferring data between Loftware Enterprise SP instances, see the "Transferring Data in a Compressed File" section of the Loftware Enterprise SP Data Transfer Guide.
Description	A description for this integration.
Integration Type	The type of integration. One of the following values is displayed: File Drop, Oracle, Cloud, SAP RFC, SAP BC-XOM, Event JMS Producer, Event JMS Consumer, Event ActiveMQ Connection, Event Amazon SQS Connection, Event Oracle AQ Connection, Event Direct Processing, Event Message Converter, Event Socket Consumer, Event File Consumer, Event File Producer, Event Email Consumer, or Event Email Producer
Configured Status	This property is not displayed until the integration has been saved for the first time. Started Stopped
Status	This property is not displayed until the integration has been saved for the first time. Service Up: The service is online. Service Down: The service is unreachable and possibly offline.
Creation Information	Created By: The user name of the creator of the integration. Created On: The date the integration was created. Modified By: The last user to change the integration. Modified On: The date the integration was last changed.