interfaces (tools & interface applications)
| Forum | Topics | Posts | Last post |
|---|
|
| 13 | 21 | by webmaster |
For PassPort / PeopleSoft shops without a lot of other PassPort interfacing requirements, this is probably the way to go for the most cost effective solution. FI Connect is pretty straight forward, with a lot of the logic contained in the .xsl and .xsd mappings.
It is necessary to push to get access to the underlying java code containing the business logic. Without access to the business logic code the project will founder.
When interfacing with PeopleSoft, getting a handle on the PeopleSoft component interfaces will be a hurdle, but the payoffs are huge. All new inbound interfaces into PeopleSoft should endeavor to use the component interfaces - the tool to provide PeopleSoft the xml doesn't matter so much.
I was floored to find this write up from IBM. IBM Global Services is still tops with me.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/indusconnect/indus11.htm
| 7 | 8 | by webmaster |
You got 'em, you hate 'em, and the programmers roll their eyes everytime the subject comes up, but there's got to be pay off to move away from them. No interface tool takes away the hard slog of figuring out the business logic.
PeopleSoft (approximately 2004) threatened to not certify installations that access their database (as in Asset Suite's database having a database link defined into PeopleSoft and updating the PeopleSoft tables), but last heard (still not so in Spring 2011), it's an empty threat because not many companies could pull off all of the inbound interfaces using PeopleSoft Integration Broker and Component Interfaces and all of the outbound working with PeopleSoft published data structure in xml. (Why didn't PeopleSoft conform to some kind of 3rd party standard like xCBL? -most likely because there is no standard for things like a Work Order (PeopleSoft Project) which makes me wonder about the value of "Systems Architect". It's not like Asset Suite's Work Order can readily be replaced by PeopleSoft's Project.) To work with the published data structure, you have to have an intimate knowledge of what it's trying to tell you about the PeopleSoft business entity (try figuring out a published Vendor with it's effective dating and pointers to addresses). It's hard, like being the president.
| 1 | 1 | by webmaster |
DataGlance, www.dataglance.com, is an example of an integration framework that allows for the integration of disparate applications. When it comes to the mapping of fields depending on this or that business rule, DataGlance provides a structured implementation. The messiest work involving cross reference tables, database access, and calls to application routines can be implemented in one application. For new PassPort installs or PassPort having to integrate with large applications besides PeopleSoft, or many applications, an integration framework is the way to go.
| 0 | 0 | n/a |
|