Beruflich Dokumente
Kultur Dokumente
Contents
The Infor ERP SyteLine MyDay Integration Guide provides implementation information for the integration
between Infor ERP SyteLine and Infor MyDay. This guide describes integration requirements and
provides setup instructions. This guide also provides information about the business events or user
actions in SyteLine that send the various business object documents (BODs) to Infor On-ramp.
Intended audience
This guide is for system administrators who implement the integration between SyteLine and MyDay, or
who need to troubleshoot or trace data back from MyDay to SyteLine.
Prerequisite
To fully understand the information presented in this guide, you should first read the Infor Open SOA
Overview Guide. The Infor Open SOA Overview Guide discusses the major concepts of Infor Open
Service Oriented Architecture (SOA) and defines common terminology. The Infor Open SOA Overview
Guide also includes a list of related documents and information on how to contact support.
Organization
The Infor ERP SyteLine MyDay Integration Guide includes these sections:
y Setup and Configuration lists the tasks that must be done before information flows from one product
to the other.
y Business events that generate BODs explains the events or user actions that cause the enterprise
resource planning (ERP) system to generate a business object document (BOD).
y Data maps explains where you can find information about the mapping between the MyDay metrics
and reports and the SyteLine tables.
Follow the steps in this section to set up the required data and connections in SyteLine, MyDay, and
associated applications.
Prerequisites
Make sure you have installed and configured all the necessary hardware and software for all of the
components. For more information, refer to these documents:
a In the Intranet field, enter the name to identify the intranet, for example: InforBUS.
b In the Description field, enter an appropriate description, for example: Infor On-Ramp
connection.
d On the General tab, from the Transport drop-down list, select ESB.
2 On the Sites/Entities form, create a logical "site" for the Infor On-Ramp:
a In the Site field, specify a name to identify this site as your On-Ramp site, for example: InforBUS.
Specify an appropriate Site Name and Description.
c In the Intranet Name field, select the intranet you created in Step 1.
• User Name - Set this field to the user ID that Infor On-Ramp will use to log into SyteLine.
This user must already be set up on the SyteLine Users form at the local site.
3 On the Sites/Entities form, configure the local site (for example, OH) to generate and/or receive
business object documents (BODs).
a On the General tab for the local site record, specify the Message Bus Logical ID for the site.
This identifies the SyteLine site to Infor On-Ramp. Specify it as lid://infor.syteline.site where site
is the name of the local site, for example lid://infor.syteline.oh. The logical ID must be all
lowercase.
Note: The logical ID entered here must match the resource component name defined in Infor
DCA for this SyteLine site, as described on page 8.
b In the Link Info tab for the local site record, add an entry with the To Site set to the On-Ramp site
(for example InforBUS).
4 Use the Tenant ID value on the Process Defaults form to specify the tenant ID. Currently you must
leave this value blank so that it defaults to infor.
− From the Source Site drop-down list, select the local site you configured in Step 3.
− From the Target Site drop-down list, select the On-Ramp site you created in Step 2.
− From the Interval Type drop-down list, select any option except Transactional.
Note: Infor has “turned off” some BOD definitions for this release by selecting some Skip check boxes in
the ESB replication category, found in the Replication Categories form. Selecting the check box ensures
that the BOD is never generated. At a later date, you may be instructed to turn on these BOD definitions
to enable integration to new metrics, reports, or products.
Form Updates
Countries Make sure existing country names are mapped to
the appropriate ISO country codes and names on
the Countries form. When adding new countries, we
recommend that you use the ISO definitions for the
countries.
Currency Codes Make sure existing currency codes and descriptions
are mapped to the appropriate ISO currency codes
and descriptions on the Currency Codes form.
When adding new currencies, we recommend that
you use the ISO codes and definitions.
Delivery Terms Make sure existing delivery terms codes are
mapped to the appropriate Incoterms codes on the
Delivery Terms form. When creating new delivery
terms, we recommend that you use the Incoterms
definitions for the terms codes.
Unit of Measure Codes Make sure existing U/M codes and descriptions are
mapped to the appropriate ISO U/M codes and
descriptions on the Unit of Measure Codes form.
When adding new U/Ms, we recommend that you
use the ISO codes and definitions.
After the data is loaded initially, SyteLine sends updates automatically when users change certain data or
certain transactions occur in SyteLine. For a list of the events that generate BODs, see See “SyteLine
business events that generate BODs” on page 10.
1 Import the enterprise template - Import the enterprise template that is provided for SyteLine
integrations, currently found in [MyDayPackage]\Installer\etc\SampleEnterpriseTemplate.xml.
Note: The appropriate file will, at some point, be available from the online registry site.
2 Create a SyteLine database resource instance - The resource for your SyteLine site database
connection should include the following settings:
− ID - Specify syteline.
− Description - Specify a description of the resource, for example SyteLine database server.
− Hostname – Specify the machine name used in the URL to connect to the SyteLine database, for
example: eagle.infor.com.
− Port – Specify the port used in the URL to connect to the SyteLine database, for example: 8080.
− Schemaname – Specify the SyteLine application database name, for example: OH_App.
− Username and password - Specify the user name and password used to log on to the SyteLine
database.
− URL - This field contains the SyteLine database server, port, and database name, in this format:
jdbc:jtds:sqlserver://dbserver:port/db_name
For example, jdbc:jtds:sqlserver://eagle.com:8080/OH_App
3 Create a component instance - The component instance for the SyteLine database resource should
include the following settings:
− ID - Specify the site name, for example, oh. This name must be lowercase. The full component
instance name shown on the COMPONENT page (infor + resource name + site name) should
match the logical ID defined in SyteLine, minus the “lid://” prefix (see page 6). Thus, if the
SyteLine logical ID is “lid://infor.syteline.oh” specify “oh” here.
− poller.deleteProcessedMessages - Specify false to allow for an audit trail during initial testing.
This setting controls the deletion of processed messages from the On-Ramp tables.
− Schemaname – Specify the SyteLine application database name, for example: OH_App.
− Username and password – Specify the user name and password used to log on to the SyteLine
database.
4 Create a routing - Specify one or more routings that the Infor On-Ramp uses to move data between
SyteLine and other Infor applications such as BIS and MDM.
To set this up, add an entry for SyteLine in the MyDay Deployments tab with these values:
Field Value
Name SyteLine
Logical ID Prefix infor.syteline
Logical ID lid://infor.syteline.site
where instance is the site name, for example oh.
This should match the logical ID defined in SyteLine.
Host Name or IP Address SyteLine host server name or IP address
Port Number (blank)
Secured No
This list explains the events (user actions) that generate a BOD from SyteLine:
Data maps
Use the documents in the ZIP file provided on Infor365 to map information between SyteLine database
tables and the elements of each BOD used with MyDay and to trace information between the SyteLine
database and the Infor Business Information Services (BIS) database. The ZIP file contains these files:
y An XML document that contains data mapping information between SyteLine database tables and the
elements of each BOD used with MyDay. The XML document also contains notes that describe
calculations or default values used in the BOD elements and the forms/windows/screens where the
data appears in SyteLine.
y Two Infor Reporting report design files that allow you to build reports based on the XML document
and a linked BIS database that contains BOD-to-MyDay export service mapping. You can filter on
columns in these reports to search for a specific MyDay export service, a specific BOD element, or
references to a specific SyteLine table or form/field combination.
y A readme file that explains how to install the report templates and set up the XML and database as
data sources for the reports.
y A PDF file containing all mapping information between SyteLine and BODs. This PDF was produced
using one of the report design files in the ZIP.
y A PDF file containing all mapping information between MyDay Export Service to SyteLine BOD
mapping and descriptions. This PDF was produced using the other report design files in the ZIP.
You will find this information especially helpful if you are used to developing custom reports based on
SyteLine and are interested in extending MyDay with new custom reports based on information in
MyDay's centralized, SOA-enabled reporting database.