book

Enterprise Application Integration

by David S. Linthicum

November 1999

Beginner to intermediate

400 pages

9h 39m

English

Addison-Wesley Professional

Read now

Unlock full access

Dedication
Why EAI?Enter ERPsWhy Write a Book on EAI?AcknowledgmentsAbout the Author
What Is EAI?Applying TechnologyHow Did Things Get This Bad?Chaos Today, Order TomorrowEvolution of StovepipesTraditional SystemsMicrocomputer SystemsDistributed SystemsPackaged ApplicationsMaking the Business Case for EAIThe Virtual Systeme-BusinessTypes of EAIMiddleware and EAI
Going for the DataData-Level EAI by ExampleDatabase-to-Database EAIFederated Database EAIConsider the Data SourceRelational DataObject-OrientedMultidimensionalOther Data Storage ModelsHierarchicalISAM and VSAMCODASYLAdabasWorking with Data-Level EAI
Application InterfacesWhat's an API?Interface by ExampleApproaching Application InterfacesThe Interface TradeoffPackaged ApplicationsPackaged Application Technology ArchitecturePackaged Application APIsTypes of ServicesTypes of InterfacesOther InterfacesVertical Market Application InterfacesSWIFTFIXHL7Custom ApplicationsRolling Your Own APIApplication WrappingUsing Application Interfaces
Method-Level ExampleWhat's a Process?ScenariosRulesLogicDataObjectsMethod WarehousingLeveraging Frameworks for EAIThe Value of FrameworksFramework FunctionalityFramework TypesService FrameworksProcedural FrameworksComponent FrameworksFramework CategoriesApplication Service FrameworksDomain FrameworksSupport FrameworksEnabling TechnologyApplication or Transaction ServersMessage BrokersDistributed ObjectsSharing Methods to Bind Your Enterprise
Leveraging User Interface-Level EAIGoing to the User InterfaceUnderstanding the ApplicationCreating the Screen CatalogMapping ScreensFinding the InformationStatic ExtractionDynamic ExtractionError ProcessingApproachesScreens-as-DataScreens-as-ObjectsEnabling TechnologyScreen Access TricksHLLAPIASCII or ANSIOLE AutomationScreens as Objects
Applying a Procedure/MethodologyStep 1: Understanding the Enterprise and Problem DomainStep 2: Making Sense of the DataIdentifying the DataThe Data DictionaryIntegrity IssuesData LatencyData FormatsData CatalogingBuilding the Enterprise Metadata ModelLogical ModelPhysical ModelNormalizing the EnterpriseStep 3: Making Sense of the ProcessesProcess IntegrationProcess CatalogingThe Common Business ModelLeveraging Patterns for Method-Level EAITypes of PatternsApplication to EAIThe Value of PatternsStep 4: Identifying Application InterfacesApplication Interface DirectoryApplication SemanticsBusiness ProcessesStep 5: Identifying the Business EventsStep 6: Identifying the Schema and Content Transformation ScenariosStep 7: Mapping Information MovementStep 8: Applying TechnologyStep 9: Testing, Testing, TestingStep 10: Considering PerformanceStep 11: Defining the ValueStep 12: Creating Maintenance ProceduresMethod or Madness?
Middleware: The Engine of EAIWhat's Middleware?Types of MiddlewareRPCsMessage-OrientedDistributed ObjectsDatabase-OrientedTransaction-OrientedTP MonitorsApplication ServersMessage BrokersMiddleware ModelsOne-to-One versus Many-to-ManyPoint-to-Point MiddlewareMany-to-Many MiddlewareSynchronous versus AsynchronousConnection-Oriented and ConnectionlessDirect CommunicationsQueued CommunicationsPublish/SubscribeRequest ResponseFire and ForgetConversational-ModeTough Choices
Notion of a TransactionThe ACID TestScalable DevelopmentDatabase MultiplexingLoad BalancingFault-ToleranceCommunicationsXA and X/OpenBuilding TransactionsApplication ServersEvolving TransactionsEnterprise JavaBeansTransactional ActiveXFuture of Transactional Middleware

RPCsDCEMessage-Oriented Middleware (MOM)MSMQUsing MSMQIBM MQSeriesMQSeries UpgradeMQSeries FeaturesMQSeries Publish/SubscribeGetting the Message
What WorksWhat's So Difficult?What's So Easy?What's a Distributed Object?The General IdeaCORBAShortfallsCORBA InternalsORBObject ServicesCommon FacilitiesApplication ObjectsCOMAutomationMoving to DCOMThe Realities
What's Database-Oriented Middleware?Types of Database-Oriented MiddlewareODBCJDBCTypes of JDBC DriversOther JDBC FeaturesJava, JDBC, and EAIOLE DBGoing NativeDatabase GatewaysEDA/SQLRDADRDAReady for Prime Time
Categories of Java Middleware StandardsDatabase-OrientedInterprocessMessage-OrientedMessaging ModelsJMS and Application DevelopmentApplication-HostingDistributed ObjectsThe Future of Java and Middleware
Why Packaged Applications?Installing Packaged ApplicationsBusiness DriversArchitectures Drive SuccessTesting What Has Already Been TestedImplementing Specific PackagesPackaged Application ToolsDatabase IssuesWeb EnablementThe OpportunityWeb-Enabled Selling and EAIIntegrating the Supply Chain (e-Business)Applying EAI to Packaged ApplicationsOur Packaged Future
The Basic ProblemSAP ArchitectureThe SAP RepositoryThe SAP Presentation LayerThe SAP Application Server LayerThe SAP Database LayerSAP MiddlewareCPI-CRFCTransactions and RFCsALEIDOCBAPIUsing the RepositorySAP and EAI
PeopleSoft ArchitectureData LevelData MoverSQRs and Moving DataWorkflow and Moving DataApplication InterfacesScreen ScrapingEDIWorkflowApplication DesignerMessage Agent APIBusiness Component APIWorkstationWhat's Best?
Defining Your e-BusinessExtending EAI outside the EnterpriseBinding the Home System to a Stranger'sThe Processe-Business TechnologyERPs and e-Businesse-Businesses Organize
The Rise of XMLWhat's XML?Data StructuresDTDsXML ParsersXML MetadataXML and MiddlewarePersistent XMLRDF and EAIXSL and EAIXML and EAI
Integration, not PerspirationWhy a New Direction?Considering the Source (and Target)Message Transformation LayerSchema ConversionsData ConversionIntelligent RoutingRules ProcessingMessage WarehousingRepository ServicesGraphical User InterfaceDirectory ServicesManagementAdaptersThin AdaptersThick AdaptersStatic and Dynamic AdaptersUsing an APITopologiesThe Future of EAI and Brokers
What Is Process Automation?Process Automation and EAI LevelsImplementing Process AutomationDocumenting ProcessesDefining ProcessesExecuting ProcessesTools and ApproachesProcess ModelingMiddleware InterfacesWorkflow StandardsProcess Automation and EAI
Problem Domains ChangeMoving from Intra- to Inter-Enterprise Application IntegrationMoving from Data-Level to Application-Level IntegrationLoose EndsSecurityPerformanceAdministrationVendor ApproachesData-OrientedData ReplicationData FederationApplication Integration–OrientedProcess Automation–OrientedTransaction-OrientedDistributed Object–OrientedTechnologies Join ForcesFuture DirectionsImportance of the ArchitectureImportance of Application DesignEAI and the Modern Enterprise

Content preview from Enterprise Application Integration

Chapter 14. Integrating SAP R/3

	Who's General Failure and why's he reading my disk?
	--Anonymous

It is no surprise that SAP R/3, the most popular packaged ERP application for the enterprise, is the packaged ERP application that most EAI architects and developers will encounter. Architects and developers tend to be pragmatic people. Knowing that most EAI products are driven by the need to move information in and out of packaged applications like SAP R/3, they figure that, unable to break free from having to link into these beasts, they might as well learn to use them to their best advantage.

As with most things, connecting to SAP has an upside and a downside. The upside is that, unlike many packaged applications out there, well-defined and well-tested ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Start your free trial

Enterprise Application Integration With XML and Java™

Publisher Resources

ISBN: 0201615835Purchase book

Enterprise Application Integration

by David S. Linthicum

Chapter 14. Integrating SAP R/3

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

You might also like