Asset Suite / PassPortGeek

Rough description of FI Connect processing to generate api message from Asset Suite to PeopleSoft.

STEP 1: Asset Suite sets trigger in table TIDYCXTR.

AS COBOL programs write triggers.

STEP 2: FI Connect poller process.

FI Connect server. Scheduled in FI Connect, Process Definition. FI Connect Process URL: http://server:port/fixml/servlet/PollerMaintenance located at ../fixml/WEB-INF/classes/icservlets/PollerMaintenance.class

Process and Schedule ID definitions are retained in files: ../fixml/regions/REGION/docs/scheduler/ProcessDefinitions.dat and ScheduleDefinitions.dat.

STEP 3: Handler.

via: ../fixml/WEB-INF/web.xml, ../fixml/docs/PPSAP.properties (constantly recreated)

Example: PPSAP.properties entry = pp.url.PuInserv=/servlet/PuInservOutboundHandler. Fires …/tomcat/webapps/fixml/WEB-INF/classes/icservlets/PuInservOutboundHandler.class

STEP 4: PeopleSoft xxxx XmlBuilder (reads data out of AS and creates XML in xxxx.xsd format).

FI Connect server .../tomcat/webapps/fixml/WEB-INF/classes/com/iint/ic/util/xml

Note: Not sure how it is known which XmlBuilder to use, i.e., should it be for SAP, Oracle, PeopleSoft.

Note: xsd and xsl files collectively make up the XSLT definition. xsd and xsl files located on FI Connect server …/tomcat/webapps/fixml/docs.

STEP 5: Message queuing.

Oracle tables tidyqhdr, tidyqref, tidyqprc. Viewable via FI Connect Message Queue.

STEP 6: XSLT (xsl file). Creates PeopleSoft xml that must match PeopleSoft message definition.

STEP 7: outboundgateway

FI Connect server .../tomcat/webapps/fixml/WEB-INF/classes/icservlets

FI Connect, Configure Financial Integration Parameters, PeopleSoft Financials Parameters