Integration technical document_v4 5.pdf

8/20/2019 Integration technical document_v4 5.pdf

1/65

SAPTCO Integration Project

INTEGRATION TECHNICAL DOCUMENT

Author: Ejada

Creation Date: 17-07-2009

Last Updated: 11-04-2010

Version: 4.5


2/65

Page ii of 65

1. Document Control

1.1 Revision History

Date Author Version Change Summary

17-7-2009 Ejada 0.1 First version03-11-2009 Ejada 0.2 Introduction section

22-01-2010 Ejada 0.7 Integration Architecture section14-02-2010 Ejada 1.0 FMS interface26-02-2010 Ejada 1.5 Informatica part03-03-2010 Ejada 2.0 CRM part

09-03-2010 Ejada 2.7 FIN part18-03-2010 Ejada 3.0 TR part

25-03-2010 Ejada 3.5 HR part26-03-2010 Ejada 4.0 EAM part

01-04-2010 Ejada 4.1 Workflow guide11-04-2010 Ejada 4.5 Adding a New Workshop-Depot Mapping

1.2 Contributors

Contributor Role Position

Ahmed KandilEmad Sarhan

1.3 Reviewers

Name Role Position Document Status Date Reviewed Comments

Incorporated

Ejada EjadaTemplate

- First version 17-7-2009

Emad Sarhan 1.5 26-02-2010Emad Sarhan 4.5 11-04-2010


3/65

Page iii of 65

Contents

1. Document Control .................................................................................... i

1.1

Revision History ......................................................................................................... i

1.2

Contributors ................................................................................................................ i

1.3

Reviewers ................................................................................................................... i

2. Introduction .............................................................................................. 1

2.1

Scope for this Document ........................................................................................... 1

2.2

Requirements for this Document ............................................................................... 1

2.3

Audience ................................................................................................................... 1

2.4

Document References .............................................................................................. 1

3. Overview ................................................................................................... 2

3.1

Abbreviations ............................................................................................................. 2

3.2

Integration Logical Architecture ................................................................................. 2

3.2.1

Integration servers ........................................................................................... 3

3.2.2

Integration schemes ........................................................................................ 3

3.3

Integration services ................................................................................................... 3

3.3.1

Services Catalog ............................................................................................. 33.3.2

Services Details ............................................................................................... 43.3.3

Services Technical Details .............................................................................. 6

4. Informatica PowerCenter Monitor Guide ............................................... 7

4.1

Opening the Workflow Monitor .................................................................................. 7

4.2

Connecting to a Repository ....................................................................................... 7

4.3

Connecting to an Integration Service ........................................................................ 8

4.4

Filtering Tasks and Integration Services ................................................................... 8

4.4.1

Filtering Tasks ................................................................................................. 84.4.2

Filtering Integration Services ........................................................................... 9

4.5

Opening and Closing Folders .................................................................................... 9

4.6

Viewing Statistics ...................................................................................................... 9

4.7

Viewing Properties .................................................................................................. 10


4/65

Page iv of 65

5. How to Monitor and Operate the Integration ....................................... 11

5.1

Informatica PowerCenter Workflows Monitoring ..................................................... 11

5.1.1

Informatica PowerCenter Workflow Monitor .................................................. 115.1.2

Workflow Notifications Emails ....................................................................... 145.1.3

Configure Informatica Extraction period:- ...................................................... 14

5.2

BPEL Processes Monitoring:- ................................................................................. 14

5.2.1

Oracle BPEL Console ................................................................................... 15

5.3

Informatica Workflows Schedulers .......................................................................... 17

5.4

Workflows Configuration Files ................................................................................. 17

6. Systems Interfaces Monitoring ............................................................. 18

6.1

CRM Interface Monitoring (FIN Integration) ............................................................ 18

6.1.1

Offline Integration .......................................................................................... 186.1.2

Online Integrations ........................................................................................ 18

6.2

CRM Interface Monitoring (TR Integration) ............................................................. 20

6.2.1

Offline Integration .......................................................................................... 20

6.2.2

Online Integrations ........................................................................................ 20

6.3

FMS Interface IVU.plan logs Monitoring ................................................................. 22

6.3.1

Application Server ......................................................................................... 226.3.2

Database server ............................................................................................ 236.3.3

TR Export Interface ....................................................................................... 236.3.4

Change exported trip classes (Add a new trip type) ..................................... 236.3.5

Maintenance Interface ................................................................................... 246.3.6

HR Interface .................................................................................................. 24

6.4

HR Interface Monitoring .......................................................................................... 25

6.5

TR Interface Monitoring ........................................................................................... 31

6.6

FIN Interface Monitoring .......................................................................................... 33

6.7

EAM-FMS Interface Follow Up Manual ................................................................... 41

6.7.1

Preventive Maintenance Interface ................................................................. 416.7.2

Corrective Maintenance Interface ................................................................. 476.7.3

Adding a New Workshop-Depot Mapping ..................................................... 51

7. Backup process ..................................................................................... 56

7.1

Systems Staging Users Database .......................................................................... 56

7.2

Integration database ............................................................................................... 56

8. Features recommendations for high availability ................................. 57

8.1

Achieving High Availability for Informatica .............................................................. 57

8.1.1

Configuring PowerCenter Internal Components for High Availability ............ 578.1.2

Minimizing Service Failover ........................................................................... 578.1.3

Optimizing Performance ................................................................................ 588.1.4

Rules and Guidelines .................................................................................... 58

8.2

Clustering the Integration Databases ...................................................................... 58


5/65

Page v of 65

8.2.1

Functionality .................................................................................................. 588.2.2

Benefits .......................................................................................................... 588.2.3

Implementation .............................................................................................. 58

9. Appendix ................................................................................................. 59


6/65

Page 1 of 65

2. Introduction

2.1 Scope for this Document

This document describes the project integrations. It describes several areas of the projectand how systems integrated with each others. After reading the document the readershould be able to operate integrations and monitor the day to day integration activities.

2.2 Requirements for this Document

This is a technical document that describes the integration project. Readers should beaware of these technologies and terminologies.

Oracle SOA Suite

Informatica Oracle Data Base SQL

2.3 Audience

This document is targeted for technical readers that will maintain the integration project. Itis expected that the reader has some technical background related to the technologiesmentioned in the previous paragraph.

2.4 Document References

Refnr.

Technology URL

1 Oracle SOA Suite http://www.oracle.com/technology/products/soa/soasuite/index.html

2 Informatica www.informatica.com/

3 Oracle Data BaseSQL

www.oracle.com

4 Oracle BPELProcess Manager

http://www.oracle.com/technology/products/ias/bpel/index.html

http://www.oracle.com/technology/products/soa/soasuite/index.htmlhttp://www.oracle.com/technology/products/soa/soasuite/index.htmlhttp://www.informatica.com/http://www.informatica.com/http://www.informatica.com/http://www.informatica.com/http://www.oracle.com/http://www.oracle.com/http://www.oracle.com/http://www.oracle.com/http://www.oracle.com/technology/products/ias/bpel/index.htmlhttp://www.oracle.com/technology/products/ias/bpel/index.htmlhttp://www.oracle.com/technology/products/ias/bpel/index.htmlhttp://www.oracle.com/http://www.informatica.com/http://www.oracle.com/technology/products/soa/soasuite/index.html


7/65

Page 2 of 65

3. Overview

The goal for the integration project is to integrate different company system according theproject scope of work. The document should help in monitoring and managing day-to-dayintegration activities

3.1 AbbreviationsThe table below surmises the abbreviations used in the integration project

Abbreviation Meaning

TR Ticketing and Reservation System

FMS Fleet Management System

CRM Seibel Customer Relationship Management System

FIN E- Business Suite Accounts Receivables and General Ledger

HR E- Business Suite Human Resources

EAM E- Business Suite Enterprise Asset Management (Maintenance)

3.2 Integration Logical Architecture

The diagram below describes the integration logical architecture


8/65

Page 3 of 65

3.2.1 Integration servers

The table below describes the integration servers and installed products

IP Name Usage Products

10.10.2.162 Integp1 Offline integration production Informatica Pow er Center 8.5.1

10.10.2.174 Integp3 Online integration production SOA Suite 10.1.3.4

10.10.2.172 Integp2 Integration test environment Informatica / SOA Suite

All servers have Windows2003 Enterprise Edition SP2 installed and Oracle RDBMS10gR2 (10.2.0.3)

3.2.2 Integration schemes

The table below describes the integration schemes and their location

Schema Name Schema location

STAGE_INTEG_USER Integration offline production database

TR_INTEG_USER Ticketing and reservation production database

FIN_INTEG_USER E-business suite production database

CRM_INTEG_USER Seibel CRM production database

3.3 Integration services

The integration service can be classified to BPEL Processes (Webservices) andInformatica Workflows (ETL) – Extract Transfer Load- also it could be classified as atomicservices and business services.

3.3.1 Services Catalog

The table below describes the integration servers catalog Producer and Consumersperspective.

Service name Producer Consumer(s)Extract Fleet Trips Data FMS DH

Process Fleet Trips Data DH DH

Export Fleet Data Trips Data DH TR

Export Stations data DH FINExport Lines data DH FINExport Carriers data DH FIN


9/65


10/65

Page 5 of 65

Export Stations data Data Hub Information InformaticaExport Lines data Data Hub Information Informatica

Export Carriers data Data Hub Information Informatica

Export Drivers data Data Hub Information Informatica

Export Vehicles data Data Hub Information Informatica

Export CRM customers Data When Siebel operators create a customer (ofType Passenger) an outbound Siebel call toTR system to create that customer record inthe TR system database and assign the

customer its ID which will be returned to CRMsystem.

SOAP over HTTP

Export TR Passenger Data When Siebel operators create a customer (ofType Passenger) an outbound Siebel call toTR system to create that customer record inthe TR system database and assign thecustomer its ID which will be returned to CRMsystem.

Informatica

Export CRM Agreements Siebel will be the owner system for MassTicketing Agreement (or contract); On Dailybasis offline integration from Siebel CRM toTR system will be done by scanning theagreement tables in CRM with type “Ticketing

Agreements” that have been created orupdated and send it to the TR system.

Informatica

Export TR Agreements update TR will be the fulfillment system for theticketing agreements, on daily basis,agreements balances will be synchronizedfrom the TR to CRM database to enabletracking agreement status in CRM.

Informatica

Export FIN Agent SDPs in TR are the points from which theuser can sell tickets or dispatch passengers.There are 2 types of SDP, Agent and Station.The agent data owner is the ERP, and thestation data owner is the FMS

Informatica

Export CRM Accounts data Siebel to send Corporate Customer and their

Addresses to finance.

Informatica

Create CRM Payment Outbound Siebel call to Finance web serviceto create a Siebel order payment information

SOAP over HTTP

Create Complete Order Outbound Siebel call to Finance web serviceto finalize the order life cycle

SOAP over HTTP

Create Order Payment Lookup Siebel to send Corporate Customer and their Addresses to finance.

SOAP over HTTP

Get Account Amount Inform about FIN Account amount SOAP over HTTP

Check In Maintenance Stay Check In Maintenance order at FMS SOAP over HTTP

Create Maintenance Stay Create In Maintenance order at FMS SOAP over HTTPModify Maintenance Stay Modify In Maintenance order at FMS SOAP over HTTP

Delete Maintenance Stay Delete In Maintenance order at FMS SOAP over HTTPExport Vehicle Dispatch Data Preventive work order SOAP over HTTPPush Fleet Dispatch Data Online web service send Dispatched

information from FMS to TR systemSOAP over HTTP

Export HR Employee Data Driver’s employee information (e.g. personaldata, leaves and Depot assignments, and ...)will be propagated from HR to FMS.

SOAP over HTTP

Data Integration Service Call web service used by TR system SOAP over HTTP

Service Lookup Provide countries, POI, gender lookups SOAP over HTTP

Service name Description Location / Protocol


11/65

Page 6 of 65

Informatica Data IntegrationService

Used to invoke Informatica service(wf2_call_FMS_TR_data_processing map)online other than schedule times

DataIntegration /SOAP over HTTP

Lookup Integration Service Used to return lookups for POI, nationality,countries

LookupsWS /SOAP over HTTP

3.3.3 Services Technical Details

The table below describes Servers Technical Details perspective.

Service name Mapping workflow / BPEL ServiceName

Location

Extract Fleet Trips Data wf1_call_FMS_WS PROD_FMS_TR

Processing Fleet TripsData

wf2_call_FMS_TR_data_processing PROD_FMS_TR

Export Fleet Trips Data wf2_call_FMS_TR_data_processing PROD_FMS_TR

Export Stations data wf3_Fill_DH PROD_FMS_TR

Export Lines data wf3_Fill_DH PROD_FMS_TR

Export Carriers data wf3_Fill_DH PROD_FMS_TR

Export Drivers data wf3_Fill_DH PROD_FMS_TRExport Vehicles data wf3_Fill_DH PROD_FMS_TR

Export Drivers TripAllowance data

wf_DH_HR_DECODE PROD_FMS_TR

Export TR Tickets data wf_TR_FIN_TICKETS PROD_FIN_TR

Export TR Services data wf_TR_FIN_SERVICE PROD_FIN_TR

Export TR Luggage data wf_TR_FIN_LUGGAGE PROD_FIN_TRExport TR InternationalCarriers data

wf_TR_FIN_INT_CARR_LOOKUP PROD_FIN_TR

Export TR ServicesLookups data

wf_TR_FIN_SERVICES_LOOKUP PROD_FIN_TR

Export FIN Agent wf_ FIN_TR_AGENTS PROD_FIN_TRExport CRM Agreements wf_CRM_AGREEMENT_TR_CONTRACT PROD_TR_CRM

Export TR Agreementsupdate

wf_TR_CONTRACTS_CRM_AGREEMENTS PROD_TR_CRM

Export CRM Accountsdata

wf1_CRM_ACCOUNTS_FIN_CUSTOMERS/ wf2_CRM_AccountAddress_FIN_Site

PROD_CRM_FIN

Export TR PassengerData

wf_m_TR_CUSTOMER_CRM_CONTACT PROD_TR_CRM

Create CRM Payment Create_CRM_Payment BPEL Server

Create Complete Order WEB-completeOrder BPEL Server

Create Order PaymentLookup

WEB-createOrderPaymentLookup BPEL Server

Get Account Amount WEB-getOnAccountAmount BPEL Server

Export CRM customersData

TRExportInterface- BaseDataPortType BPEL Server

Check In MaintenanceStay

WorkshopService-checkinMaintenanceStay BPEL Server

Create Maintenance Stay WorkshopService-createMaintenanceStay BPEL Server

Modify Maintenance Stay WorkshopService-modifyMaintenanceStay BPEL ServerDelete Maintenance Stay WorkshopService-deleteMaintenanceStay BPEL ServerExport Vehicle DispatchData

VehicleDispatchVehicleWorking-exportVehicleDispatchVehicleWorking

BPEL Server

Push Fleet Dispatch Data TripPortType-importDispatchedTrips BPEL Server

Export HR DataEmployee

PersonnalImport-importEmployees BPEL Server


12/65

Page 7 of 65

4. Informatica PowerCenter Monitor Guide

The Workflow Monitor provides options to view information about workflow runs. Afteryou open the Workflow Monitor and connect to a repository, you can view dynamicinformation about workflow runs by connecting to an Integration Service.

You can customize the Workflow Monitor display by configuring the maximum days orworkflow runs the Workflow Monitor shows. You can also filter tasks and Integration

Services in both Gantt Chart and Task view.

Complete the following steps to monitor workflows:

1. Open the Workflow Monitor. 2. Connect to the repository containing the workflow. 3. Connect to the Integration Service. 4. Select the workflow you want to monitor. 5. Select Gantt Chart view or Task view.

4.1 Opening the Workflow Monitor

You can open the Workflow Monitor in the following ways:

Select Start > Programs > Informatica PowerCenter [version] > Client >Workflow Monitor from the Windows Startmenu. Configure the Workflow Manager to open the Workflow Monitor when you run a workflow from the WorkflowManager. Click Tools > Workflow Monitor from the Designer, Workflow Manager, or Repository Manager. Or, click theWorkflow Monitor icon on the Tools toolbar. When you use a Tools button to open the Workflow Monitor,PowerCenter uses the same repository connection to connect to the repository and opens the same folders.

You can open multiple instances of the Workflow Monitor on one machine using theWindows Start menu.

To open the Workflow Monitor when you start a workflow:

1.In the Workflow Manager, click Tools > Options. 2.In the General tab, select Launch Workflow Monitor When Workflow Is Started.

To open the Workflow Monitor from the Workflow Manager:

1.In the Workflow Manager, connect to a repository. 2.In the Navigator, right-click an Integration Service or a repository and select Run Monitor. The Workflow Monitor appears.

4.2 Connecting to a Repository

When you open the Workflow Monitor, you must connect to a repository. Connect torepositories by clicking Repository > Connect. Enter the repository name and connectioninformation.

After you connect to a repository, the Workflow Monitor displays a list of Integration

Services available for the repository. The Workflow Monitor can monitor multiplerepositories, Integration Services, and workflows at the same time.

Note: If you are not connected to a repository, you can remove the repository from the Navigator.Select the repository in the Navigator and click Edit > Delete. The Workflow Monitor displays amessage verifying that you want to remove the repository from the Navigator list. Click Yes toremove the repository. You can connect to the repository again at any time.


13/65

Page 8 of 65

4.3 Connecting to an Integration Service

When you connect to a repository, the Workflow Monitor displays all Integration Servicesassociated with the repository. This includes active and deleted Integration Services. Tomonitor tasks and workflows that run on an Integration Service, you must connect to theIntegration Service. In the Navigator, the Workflow Monitor displays a red icon overdeleted Integration Services.

To connect to an Integration Service, right-click it and select Connect. When you connect

to an Integration Service, you can view all folders that you have permission for. Todisconnect from an Integration Service, right-click it and select Disconnect. When youdisconnect from an Integration Service, or when the Workflow Monitor cannot connect toan Integration Service, the Workflow Monitor displays disconnected for the IntegrationService status.

The Workflow Monitor is resilient to the Integration Service. If the Workflow Monitor losesconnection to the Integration Service, LMAPI tries to reestablish the connection for theduration of the PowerCenter Client resilience time-out period. For more information aboutresilience, see the PowerCenter Administrator Guide.

After the connection is reestablished, the Workflow Monitor retrieves the workflow statusfrom the repository. Depending on your Workflow Monitor advanced settings, you mayhave to reopen the workflow to view the latest status of child tasks. For more informationabout the Workflow Manager advanced settings.

You can also ping an Integration Service to verify that it is running. Right-click theIntegration Service in the Navigator and select Ping Integration Service. You can view theping response time in the Output window.

Note: You can also open an Integration Service in the Navigator without connecting to it. Whenyou open an Integration Service, the Workflow Monitor gets workflow run information stored in therepository. It does not get dynamic workflow run information from currently running workflows.

4.4 Filtering Tasks and Integration Services

You can filter tasks and Integration Services in both Gantt Chart view and Task view. Usethe Filters menu to hide tasks and Integration Services you do not want to view in theWorkflow Monitor.

4.4.1 Filtering Tasks

You can view all or some workflow tasks. You can filter tasks you do not want to view.For example, if you want to view only Session tasks, you can hide all other tasks. Youcan view all tasks at any time.

You can also filter deleted tasks. To filter deleted tasks, click Filters > Deleted Tasks.

To filter tasks:1.Click Filters > Tasks. 2.Clear the tasks you want to hide, and select the tasks you want to view.3.Click OK.

Note: When you filter a task, the Gantt Chart view displays a red link between tasks to indicate afiltered task. You can double-click the link to view the tasks you hid.


14/65

Page 9 of 65

4.4.2 Filtering Integration Services

When you connect to a repository, the Workflow Monitor displays all Integration Servicesassociated with the repository. You can filter out Integration Services to view onlyIntegration Services you want to monitor.

When you hide an Integration Service, the Workflow Monitor hides the Integration Servicefrom the Navigator for the Gantt Chart and Task views. You can show the IntegrationService again at any time.

You can hide unconnected Integration Services. When you hide a connected IntegrationService, the Workflow Monitor asks if you want to disconnect from the Integration Serviceand then filter it. You must disconnect from an Integration Service before hiding it.

To filter Integration Services:

1.In the Navigator, right-click a repository to which you are connected and select Filter Integration Services.-or-Connect to a repository and click Filters > Integration Services.The Filter Integration Services dialog box appears.

2.Select the Integration Services you want to view and clear the Integration Services you want to filter. Click OK. If you are connected to an Integration Service that you clear, the Workflow Monitor prompts you to disconnect from

the Integration Service before filtering.3.Click Yes to disconnect from the Integration Service and filter it.The Workflow Monitor hides the Integration Service from the Navigator.Click No to remain connected to the Integration Service. If you click No, you cannot filter the Integration Service.

Tip: To filter an Integration Service in the Navigator, right-click it and select Filter IntegrationService.

4.5 Opening and Closing Folders

You can select which folders to open and close in the Workflow Monitor. When you opena folder, the Workflow Monitor displays the number of workflow runs that you configuredin the Workflow Monitor options. For more information.

You can open and close folders in the Gantt Chart and Task views. When you open afolder, it opens in both views. To open a folder, right-click it in the Navigator and selectOpen. Or, you can double-click the folder.

4.6 Viewing Statistics

You can view statistics about the objects you monitor in the Workflow Monitor. Click View> Statistics. The Statistics window displays the following information:

Number of opened repositories. Number of repositories you are connected to in the Workflow Monitor. Number of connected Integration Services. Number of Integration Services you connected to since you openedthe Workflow Monitor. Number of fetched tasks. Number of tasks the Workflow Monitor fetched from the repository during the period

specified in the Time window.


15/65

Page 10 of 65

4.7 Viewing Properties

You can view properties for the following items:

To view properties for all objects, right-click the object and select Properties. You canright-click items in the Navigator or the Time window in either Gantt Chart view or Taskview.

To view link properties, double-click the link in the Time window of Gantt Chart view.

When you view link properties, you can double-click a task in the Link Properties dialogbox to view the properties for the filtered task.


16/65

Page 11 of 65

5. How to Monitor and Operate the Integration

The Workflow Monitor provides options to view information about workflow runs. Afteryou open the Workflow Monitor and connect to a repository, you can view dynamicinformation about workflow runs by connecting to an Integration Service.

5.1 Informatica PowerCenter Workflows Monitoring

In this section we describe how to monitor Informatica Workflows, we could use three ways to do that

1. Informatica PowerCenter Workflow Monitor2. Workflow Notifications Emails

5.1.1 Informatica PowerCenter Workflow Monitor

To monitor, administrate and operate Integration Service for Informatica Workflows the responsible for thisshould be familiars with “Informatica PowerCenter Workflow Monitor ” tool.

The “Informatica PowerCenter Workflow Monitor ” tool used to

Control and Manage. Stop or aborts workflows also restart workflows.

Monitor . Verify succeeded or failed workflows and which workflows are scheduled.

Get Log Events for workflows and sessions logs: used to get internal Informatica Log screen.

Control and Manage


17/65

Page 12 of 65

Monitor


18/65

Page 13 of 65

Get Log Events for workflows and sessions logs

Workflows and Sessions logs


19/65

Page 14 of 65

5.1.2 Workflow Notifications Emails

This is an additional way to monitor workflows success/ fail completion using emails notifications weshould log in into [email protected] and check email Inbox using Outlook programs or Web access

5.1.3 Configure Informatica Extraction period:-

To allow integration to be parameterized to accept the extraction period from FMS to TR system Integration stuff

should change parameter file mentioned below to be reflected at daily scheduled workflow which extracted Trips datainto TR system. As below table

# Parameter For one monthvalue includingrunning month

For three monthvalue includingrunning month

For three month valueNOT includingrunning month

1 $$DAYES_BEFORE_SYSDATE 1 1 -30

2 $$DAYES_OF_WINDOW 31 91 91

File path %INFORMATICA%\server\infa_shared\SrcFiles\PARAMETERS_DATA\TR_WINDOW.TXT

5.2 BPEL Processes Monitoring:-

In this section we describe how to monitor BPEL (Business Process Execution Language) Processes, Use below wayto do that

1. Oracle BPEL Console

mailto:[email protected]:[email protected]:[email protected]:[email protected]


20/65

Page 15 of 65

5.2.1 Oracle BPEL Console

To monitor online interfaces the responsible for this should be familiars with “Oracle BPEL Console” tool. The “Oracle BPEL Console” tool used to:-

Monitor Completed Process. Verify succeeded or failed Process and which BPEL are called.

Get History for BPEL Process: used to get internal BPEL Log.

Login into BPEL Console


21/65

Page 16 of 65

Browse completed process

Check BPEL history


22/65

Page 17 of 65

Audit BPEL process

5.3 Informatica Workflows Schedulers

# Integration Point Scheduling Time

1 CRM-FIN 1:00 AM

2 TR-FIN Run every twohours starting from1:00 AM each day

3 FMS-TR 2:30 AM

4 FMS-HR 2:30 AM

5 CRM-TR 12:00 AM 4:00 AM 8:00 AM 12:00 PM4:00 PM8:00 PM

5.4 Workflows Configuration Files

Under %INFORMATCIA%\server\infa_shared_SrcFiles\PARAMETERS_DATA all configurationfiles are located in one place to easy configure workflows parameters.


23/65

Page 18 of 65

6. Systems Interfaces MonitoringIn this section we will start to describe monitoring tasks in other systems. It contains below manuals

6.1 CRM Interface Monitoring (FIN Integration)

6.1.1 Offline IntegrationTo debug any EIM job you will find the log for this job in the following path:

\\[Application Server]\C$\sea78\siebsrvr\log\EIM_XXXXX.log

In this log you will findLoading initial configuration file "MassTicketingImport.ifb".And for every base table you will find the number of Inserted, Failed, Updated, and duplicated rows same asthe following: IF table: EIM_AGREEMENT, Base Table: S_DOC_AGREE, Initial: 29, Failed: 0, Duplicate: 29, Inserted: 0, Updated:0, Total Time: 0.08s, Row Time: 0s

The names of ifb files for FIN offline integrations are:a- AccountExport.ifb

6.1.2 Online Integrations

All online integration processes are represented as a workflow in Siebel.Online Integration workflows for the FIN system are the following:

a- SAPTCO FIN Complete Orderb- SAPTCO FIN Get On Accountc- SAPTCO FIN Create Order Lookupd- SAPTCO Create CRM Payment

To monitor any workflow you have to do the following:

1- Login to the Siebel application with an administrator privilege2- Go to Site map - > Administration – Business Process -> Workflow Deployment.


24/65

Page 19 of 65

3- Query for the workflow name in Active Workflow Processes4- Select the Monitor Level as Detail.5- Go to Workflow Instance Monitor.6- Query for the workflow name and the required instance.

7- Go to Step Instances and you will find all the details related to the execution steps for the requiredworkflow instance.


25/65


26/65

Page 21 of 65

To monitor any workflow you have to do the following:8- Login to the Siebel application with an administrator privilege9- Go to Site map - > Administration – Business Process -> Workflow Deployment.

10- Query for the workflow name in Active Workflow Processes11- Select the Monitor Level as Detail.12- Go to Workflow Instance Monitor.13- Query for the workflow name and the required instance.

14- Go to Step Instances and you will find all the details related to the execution steps for the requiredworkflow instance.


27/65

Page 22 of 65

6.3 FMS Interface IVU.plan logs Monitoring

6.3.1 Application Server

Technical application server logs are to be found in

\\fmsappp1\c$\ Z:\JBoss\4.2.3.GA_-1_MB@ivu_FMSDBP1\server\default\log

Standard logsLog name Description

boot.log Application server startup log

error.log Any log messages with level “Error” or higher

hql.log HQL log messages (disabled)

server.log General log messages with level “Info“ or higher

sql.log SQL log messages (disabled)

wrapper.log All log messages with level “Info” or higher

Administrative problems like network failures, out-of-memory problems etc. can all be found in boot.log or server.log

wrapper.log (this is a catch all log written by the Windows service wrapper for Java).

error.log

However, not every “Error” log message in these files points to administrative problems or a real problem at all. Forexample, errors reporting “EJBTransactionRolledBackException” are generally handled by the concerned IVU.planapplications or interfaces.


28/65

Page 23 of 65

IVU-specific logsThese log files contain technical log messages of IVU.plan applications or interfaces. They are generally onlyunderstandable by the respective IVU developers. The set of these files and their configuration might change any timewithout notice.

Currently, these include ivu*.log, saptco-*.log and usecase.log.

6.3.2 Database serverDatabase startup problems can be found in c:\oracle\102srv_64\database\oradim.log on fmsdbp1. The are no specificIVU.plan logs.

6.3.3 TR Export Interface

The TR export interfaces (on- and offline) write log files for users to a configurable path on the app-server. The defaultpath is \\fmsappp1\c$\tr-export-interface-output .

There are 4 kinds of files, which are described in the following subsections. Each of them includes a timestamp aspart of the name. Files with the same timestamp belong to the same export.

When problems where handled, the respective files should be deleted to save disk space (especially the *.xml files).

invalid-data-messages-.txtThese files contain messages regarding problematic data in IVU.plan. They should be regularly checked by SAPTCOusers.

Issues reported here include conflicting trips, stops without stop type or stop area, and mismatches between dispatchand planning data (most likely due to defective duties or vehicle workings).

other-error-messages-.txtThese files are produced only if there were technical error messages that caused the export to fail. If so, a messagereporting the failure is included.

For the online interface, this includes cases where the call to the TR online webservice failed or where that

service returned a non-success error. In these cases, the online export will be tried again in the interface’s

next run. Thus, the situation is only problematic if these files appear repeatedly for subsequent exports.

For the offline interface, this includes cases where the response to the TR offline service failed. The TR

system should recognize and handle such cases.

For both interfaces, it also includes cases where the export data could not be obtained (e.g. due to illegal app-

server state or if the database if offline). In these cases, a technical Exception and stack trace is included. It

should first be checked whether app-server and database are running OK (e.g. by starting Personnel

Dispatch). Otherwise, the error should be reported to IVU.

online-export-.xmlThe data payload of the respective online-export.

offline-export-.xmlThe data payload of the respective offnline-export.

6.3.4 Change exported trip classes (Add a new trip type)

To add a new trip type or remove a trip type from TR exported list, the below steps should be done by one of IVU staffmember because it has an extremely effect on FMS-TR integration.

1. Open http://fmsappp1:30010/jmx-console/ (FMS Interface URL)

http://fmsappp1/c$/tr-export-interface-outputhttp://fmsappp1/c$/tr-export-interface-outputhttp://fmsappp1/c$/tr-export-interface-outputhttp://fmsappp1:30010/jmx-console/http://fmsappp1:30010/jmx-console/http://fmsappp1:30010/jmx-console/http://fmsappp1:30010/jmx-console/http://fmsappp1/c$/tr-export-interface-output


29/65

Page 24 of 65

2. Under “saptco”, open link “TRExportInterfaceConfigurationService”

3. Edit the field “ExportedTripClasses”, a comma separated list of the trip classes which are exported.

4. Click “Apply Changes” button.

6.3.5 Maintenance Interface

Maintenance stay booking interfaceVehicle dispatch users should regularly check whether maintenance stay bookings are OK.

For this, in the vehicle dispatch application, open System->Log. This log includes messages from the maintenancestay booking interface regarding

1. errors in creating imported maintenance stays including reason. Depending on the reason, the situation

should either be resolved by vehicle dispatch users or maintenance system users.

2. overlaps of maintenance stays with vehicle working assignments. This should be resolved by vehicle

dispatch users by either changing the respective vehicles’ assignments or requesting maintenance system

users to change the maintenance stays.Vehicle working export interface Any problems are reported in the response of the vehicle working export service to the maintenance system. Thisregards only technical errors. It should first be checked whether app-server and database are running OK (e.g. bystarting Personnel Dispatch). Otherwise, the error should be reported to IVU.

6.3.6 HR Interface

Any problems are reported in the response of the personnel import service to the HR system. This includes

Inconsistent data messages: they point out illegal import data regarding e.g. inconsistencies of staff

membership and depot assignments or unavailabilities. They should be resolved by HR system users.

FMS update or other error messages: these point to technical import failures. It should first be checked

whether app-server and database are running OK (e.g. by starting Personnel Dispatch). Otherwise, the error

should be reported to IVU.


30/65

Page 25 of 65

6.4 HR Interface Monitoring

To monitor HR-FMS interface you have to login to ERP system as administrator. And follow up below guide

[1] Open the “Requests” window as follows:


31/65

Page 26 of 65

[2] Query for the request whose name starts with INTEGRATION , as follows :


32/65

Page 27 of 65

You should find something like the following:

This request runs every night at 9:00 pm; a new copy of the request is submitted automatically to be run the nextnight.

This new copy of the request will be pending like below (its status is highlighted in green).


33/65

Page 28 of 65

[3] Check the execution of the interface on the last night as follows:

Go to the line of the last night’s execution (the line just under the pending request line):

Check the Two Columns “Phase” and “Status”.

The “phase” should be Completed and the status should be Normal. If status is Error, you should check the log, aswe will see shortly.

To make sure of the date of execution, click the “View Details” Button


34/65

Page 29 of 65

[4] Check the “Date Started”, “Date Completed” of the request, as follows:


35/65

Page 30 of 65

[5] Check the log:

You should check the log every day even if the request is completed normally.

You can check the log by pressing the “View Log” button, as follows:


36/65

Page 31 of 65

[6] Search in the log for the following message titles:

1- Incomplete data

2- Inconsistent data

3- Duplicate elements of the same type given for the same employee

4- FMS data update error

5- Other error

For the first three messages send the error message to HR department to fix the situation described.

For messages 4 and 5, Contact Ejada.

If you see something like the following, Contact Ejada

6.5 TR Interface Monitoring

This paragraph describe how to monitor integration within TR screens, follow up below screens, you have to be TRadministrator user.


37/65

Page 32 of 65


38/65

Page 33 of 65

6.6 FIN Interface Monitoring

To monitor TR-FIN interface you have to login to ERP system as administrator. And follow up below guide



39/65

Page 34 of 65

[2] Query for the request whose name: اذاكر

بنظم

اصة

اىة

قىد

و

افىاتر

:, as followsترحل


40/65

Page 35 of 65


This request runs every night at 4:00 am; a new copy of the request is submitted by informatica to be run theintegration.


41/65

Page 36 of 65


Go to the line of the last night’s execution:





42/65

Page 37 of 65

[4] Check the “Date Started”, “Date Completed” of the request, as follows:


43/65

Page 38 of 65

[5] Check the log:

You should check every day even if the request is completed normally, if there are some tickets still notposted to Finance, using the following concurrent program:

طخ هب يا ركاذا

.


44/65

Page 39 of 65

Then you should check the output by pressing the “View output” button, as follows:


45/65

Page 40 of 65

[6] If there is any error code with any ticket you should solve this problem by reference to the error code and itsdescription at the end of the report


46/65

Page 41 of 65

If you see something like the following, Contact Ejada

6.7 EAM-FMS Interface Follow Up Manual

6.7.1 Preventive Maintenance Interface



47/65

Page 42 of 65


48/65

Page 43 of 65

[2] Query for the request whose name starts with “INTEGRATION: Preventive”, as follows:


49/65

Page 44 of 65


This request runs every night at 9:00 pm; a new copy of the request is submitted automatically to be run the nextnight.

This new copy of the request will be pending like below (its status is highlighted in green).


50/65

Page 45 of 65


Go to the line of the last night’s execution (the line just under the pending request line):





51/65

Page 46 of 65

[5] Check the log:

You should check the log every day even if the request is completed normally.

You can check the log by pressing the “View Log” button, as follows:

If the log contains any errors, contact the system administrator.


52/65

Page 47 of 65

6.7.2 Corrective Maintenance Interface



53/65

Page 48 of 65

[2] Query for the request whose name starts with “INTEGRATION: Corrective”, as follows:


54/65

Page 49 of 65


This request runs every 10 minutes.

The completed run of the request should have phase = “Completed” and Status = “Normal”.


55/65

Page 50 of 65

[5] In case a work order of a bus is not sent, you can check the log, by pressing the “View Log” button, as follows:

This will open the log in internet explorer:

You can search of the bus number by pressing CTRL+F, as follows:


56/65

Page 51 of 65

6.7.3 Adding a New Workshop-Depot Mapping

This guide describes how to add a new mapping between a fleet system network point and a maintenance workshop:

Suppose we have a new network point whose code is P_POINT and its name is “New Point”, there’s a new workshopat this point whose code is W_NEW

To add the mapping between the network point and the workshop, do the following:

[1] Under the “Enterprise Asset Management” Responsibility

Navigate to the “Lookups” window

Setup > Lookups


57/65

Page 52 of 65


58/65

Page 53 of 65

[2] Click the link, The Lookups form will open:


59/65

Page 54 of 65

[3] Query for lookup type EAM_DEPOTS_WORKSHOPS_MAPPING:

The existing Mappings will appear in the details:

The “code” fields contains the code of the fleet system network point code (whether it’s a depot or any other networkpoint)

The “Meaning” column contains the maintenance workshop (department) code

The “Description” column contains the name of place where the fleet network point exist.


60/65

Page 55 of 65

[3] Create a new record and add the data of the new mapping as follows:

Save by pressing on the save button in the tool bar.


61/65

Page 56 of 65

7. Backup process

To keep last up and running version of Stage DataBase users, the below schemas haveto be backup regularly.

7.1 Systems Staging Users Database

With each system backup below schemas have to be backup

TR_INTEG_USER must be backup with TR system.FIN_INTEG_USER must be backup with FIN system.CRM_INTEG_USER must be backup with CRM system.

7.2 Integration database

STAGE_INTEG_USER must be backup separately, but within the same period of backup to other systems.


62/65

Page 57 of 65

8. Features recommendations for high availability

New Features and recommendations for Integration Services can be applied to belowareas.

Achieving High Availability for Informatica Clustering the Integration databases

Describe how to make this is listed in below paragraphs.

8.1 Achieving High Availability for Informatica

You can achieve different degrees of availability depending on factors that are internaland external to the PowerCenter environment. For example, you can achieve a greaterdegree of availability when you configure more than one node to serve as a gateway andwhen you configure backup nodes for application services.

Consider internal components and external systems when you are designing a highlyavailable PowerCenter environment:

Internal components. Configure nodes and services for high availability. External systems. Use highly available external systems for hardware, shared storage, database systems,

networks, message queues, and FTP servers.

8.1.1 Configuring PowerCenter Internal Components for High Availability

PowerCenter internal components include the Server Manager, nodes, and all serviceswithin the PowerCenter environment. You can configure nodes and services to enhanceavailability:

Configure more than one gateway. You can configure multiple nodes in a domain to serve as the gateway. Onlyone node serves as the gateway at any given time. That node is called the master gateway. If the master gatewaybecomes unavailable, the Service Manager elects another master gateway node. If you configure only one gatewaynode, the gateway is a single point of failure. If the gateway node becomes unavailable, the Service Manager cannotaccept service requests.Configure application services to run on multiple nodes. You can configure the application services to run on

multiple nodes in a domain. A service is available if at least one designated node is available. Configure access to shared storage. You need to configure access to shared storage when you configure multiplegateway nodes and multiple backup nodes for the Integration Service. When you configure more than one gatewaynode, each gateway node must have access to the domain configuration database. When you configure theIntegration Service to run on more than one node, each node must have access to the run-time files used to processa session or workflow.

When you design a highly available PowerCenter environment, you can configure thenodes and services to minimize failover or to optimize performance.

Minimize service failover. Configure two nodes as gateway. Configure different primary nodes for each applicationservice.Optimize performance. Configure gateway nodes on machines that are dedicated to serve as a gateway. Configurebackup nodes for the Integration Service and the Repository Service.

8.1.2 Minimizing Service Failover

To minimize service failover in a domain with two nodes, configure the IntegrationService and Repository Service to run on opposite primary nodes. Configure one node asthe primary node for the Integration Service, and configure the other node as the primarynode for the Repository Service.


63/65

Page 58 of 65

8.1.3 Optimizing Performance

To optimize performance in a domain, configure gateway operations and applicationsservices to run on separate nodes. Configure the Integration Service and the RepositoryService to run on multiple worker nodes. When you separate the gateway operationsfrom the application services, the application services do not interfere with gatewayoperations when they consume a high level of CPUs.

8.1.4 Rules and Guidelines

Use the following rules and guidelines when you set up high availability for thePowerCenter environment:

Install and configure PowerCenter services on multiple nodes. For each node, configure Informatica Services to restart if it terminates unexpectedly. In the Administration Console, configure at least two nodes to serve as gateway nodes. Configure the Repository Services to run on at least two nodes. Configure the Integration Services to run on multiple nodes. Configure primary and backup nodes or a grid. If youconfigure the Integration Services to run on a grid, make resources available to more than one node. Use highly available database management systems for the repository databases associated with RepositoryServices and the domain configuration database.

Tip: To perform maintenance on a node without service interruption, disable the service process

on the node so that the service will fail over to a backup node.

8.2 Clustering the Integration Databases

Oracle Real Application Clusters (RAC) is an option to the award-winning Oracle Database Enterprise Edition. OracleRAC is a cluster database with a shared cache architecture that overcomes the limitations of traditional shared-nothing and shared-disk approaches to provide highly scalable and available database solutions for all your businessapplications. Oracle RAC is a key component of Oracle enterprise grid architecture.

8.2.1 Functionality

Oracle RAC allows multiple computers to run Oracle RDBMS software simultaneously while accessing a singledatabase, thus providing a clustered database.In a non-RAC Oracle database, a single instance accesses a single database. Where the "database" consists of acollection of data files, control files, and redo logs located on disk; the "instance" comprises the collection of Oracle-related memory and operating system processes that run on a computer system.In an Oracle RAC environment, two or more computers (each with an instance) concurrently access a singledatabase. This allows an application or user to connect to either computer and have access to a single coordinatedset of data.

8.2.2 Benefits

Since Oracle RAC allows multiple computers (instances) to access a single database simultaneously, it addressesseveral areas of database management. These areas include:

fault tolerance load balancing scalability

8.2.3 Implementation

Oracle RAC depends on the infrastructure component Oracle Cluster ware to coordinate multiple servers and theirsharing of data storage.

http://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Databasehttp://en.wikipedia.org/wiki/Computer_clusterhttp://en.wikipedia.org/wiki/Instancehttp://en.wikipedia.org/wiki/Data_filehttp://en.wikipedia.org/wiki/Redo_loghttp://en.wikipedia.org/wiki/Disk_storagehttp://en.wikipedia.org/wiki/Operating_systemhttp://en.wikipedia.org/wiki/Fault_tolerancehttp://en.wikipedia.org/wiki/Load_balancing_%28computing%29http://en.wikipedia.org/wiki/Scalabilityhttp://en.wikipedia.org/wiki/Infrastructurehttp://en.wikipedia.org/wiki/Oracle_Clusterwarehttp://en.wikipedia.org/wiki/Oracle_Clusterwarehttp://en.wikipedia.org/wiki/Infrastructurehttp://en.wikipedia.org/wiki/Scalabilityhttp://en.wikipedia.org/wiki/Load_balancing_%28computing%29http://en.wikipedia.org/wiki/Fault_tolerancehttp://en.wikipedia.org/wiki/Operating_systemhttp://en.wikipedia.org/wiki/Disk_storagehttp://en.wikipedia.org/wiki/Redo_loghttp://en.wikipedia.org/wiki/Data_filehttp://en.wikipedia.org/wiki/Instancehttp://en.wikipedia.org/wiki/Computer_clusterhttp://en.wikipedia.org/wiki/Databasehttp://en.wikipedia.org/wiki/Relational_database_management_system


64/65

Page 59 of 65

9. Appendix

Buffer memoryBuffer memory allocated to a session. The Integration Service uses buffer memory to move data from sources totargets. The Integration Service divides buffer memory into buffer blocks.

Buffer memory size

Total buffer memory allocated to a session specified in bytes or as a percentage of total memory.

Concurrent workflow A workflow configured to run multiple instances at the same time. When the Integration Service runs a concurrentworkflow, you can view the instance in the Workflow Monitor by the workflow name, instance name, or run ID.

High availability A PowerCenter option that eliminates a single point of failure in a domain and provides minimal service interruption inthe event of failure.

Log Agent A Service Manager function that provides accumulated log events from session and workflows. You can view sessionand workflow logs in the Workflow Monitor. The Log Agent runs on the nodes where the Integration Service process

runs.

Log Manager A Service Manager function that provides accumulated log events from each service in the domain. You can view logsin the Administration Console. The Log Manager runs on the master gateway node.

Mapping A set of source and target definitions linked by transformation objects that define the rules for data transformation.

Node A logical representation of a machine or a blade. Each node runs a Service Manager that performs domain operationson that node.

One-way mapping A mapping that uses a web service client for the source. The Integration Service loads data to a target, often triggeredby a real-time event through a web service request.

PowerCenter resource Any resource that may be required to run a task. PowerCenter has predefined resources and user-defined resources.

PowerCenter servicesThe services available in the PowerCenter domain. These consist of the Service Manager and the applicationservices. The application services include the Repository Service, Integration Service, Reporting Service, MetadataManager Service, Web Services Hub, and SAP BW Service.

Real-time dataData that originates from a real-time source. Real-time data includes messages and messages queues, web servicesmessages, and changed source data.

Real-time processingOn-demand processing of data from operational data sources, databases, and data warehouses. Real-timeprocessing reads, processes, and writes data to targets continuously.

Real-time session A session in which the Integration Service generates a real-time flush based on the flush latency configuration and alltransformations propagate the flush to the targets.


65/65

Service workflow A workflow that contains exactly one web service input message source and at most one type of web service outputmessage target. Configure service properties in the service workflow.

Session A session is a set of instructions or a type of task that tells the Integration Service how and when to move data fromsources to targets.

Workflow A set of instructions that tells the Integration Service how to run tasks such as sessions, email notifications, and shellcommands.

Workflow instanceThe representation of a workflow. You can choose to run one or more workflow instances associated with aconcurrent workflow. When you run a concurrent workflow, you can run one instance multiple times concurrently, oryou can run multiple instances concurrently.

Workflow run ID A number that identifies a workflow instance that has run.

Worklet A worklet is an object representing a set of tasks created to reuse a set of workflow logic in multiple workflows.

BPELBusiness Process Execution Language for Web services is an XML-based language designed to enable task-sharingfor a distributed computing or grid computing environment - even across multiple organizations - using a combinationof Web services.

Integration technical document_v4 5.pdf

Documents

Transcript of Integration technical document_v4 5.pdf