What issues should be considered for enterprise integration (. NET/J2EE perspective)

. NetView

LKeep it simple, but not simpler(-- Einstein)

LIs easy for developers to implement

LDefine the integration scope and target system to be integrated/Application/Process

LSort the call relationships and clarify the boundaries of each integration target and the trust relationships between the boundaries.

LIs there a standard development environment?

LCan implementation be completed as soon as possible (implementation-effectiveness-implementation in the next stage)

LWhether or not the lower-layer technical environment and upper-layer business processing have been abstracted and stripped out, otherwise the integration will increase complexity

LApplicable?P & PSeriesIntegration patternsMentioned inMessage Broker,Message Bus,P2P connectionScenario

LBreak down the integration work and adoptPortalIntegration? Data integration? Function integration? Establish an independent data center (for security integration, you also need to consider whether to establishPKICenter, for exampleAdAsCAOr a third-partyCAAnd provideSSOAnd certificate boundary ing)

LNeed to add newEndpoint

LCan I add a stored procedure and use it together?JDBCInstead of directly modifyingCICs,COBOLAnd other platform development business logic

LWhether to pass unifiedWCF/BizTalk/SQL Service BrokerTechnical implementation of distributed calls to legacy platforms and heterogeneous platforms

LWhether business processing can complete transactions without knowing the underlying technical system (that is, whether the underlying technical services and upper-layer business processing are effectively isolated)

LIf the change is processed at the backend, what will the impact on the upper-layer business processes and applications? (especially those in the enterprise that have the"Core"Process or application), whether or not to refactor the lower layer

LWhich one to choose?. NetLanguage? Or which. NetLanguage-oriented?

LWhat technologies does your company use?ODBC/ole db/ADO. Net/LINQ & Entity Framework?MSMQ/IBM MQ(BeaOfMessageqUnless you have to, don't worry about it. You have to integrate it again )?WCF/. Net remoting/Enterprise Service/socket/WS -*?

LUsed?Entlib 3.1/4.0Replace with part What is the public component platform of the "half-old" system?

LWhether to consider usingSharePointOfWeb Part?

Java/J2EEView

LKeep it simple, but not simpler(-- Einstein)

LIs easy for developers to implement

LDefine the integration scope and target system to be integrated/Application/Process

LSort the call relationships and clarify the boundaries of each integration target and the trust relationships between the boundaries.

LIs there a standard development environment?

LCan implementation be completed as soon as possible (implementation-effectiveness-implementation in the next stage)

LWhether or not the lower-layer technical environment and upper-layer business processing have been abstracted and stripped out, otherwise the integration will increase complexity

LNeed to add newConnector

LCan I add a stored procedure and use it together?JDBCInstead of directly modifyingCICs,COBOLAnd other platform development business logic

LWhether business processing can complete transactions without knowing the underlying technical system (that is, whether the underlying technical services and upper-layer business processing are effectively isolated)

LIf the change is processed at the backend, what will the impact on the upper-layer business processes and applications? (especially those in the enterprise that have the"Core"Process or application), whether or not to refactor the lower layer

L what technology does your company use? j2c , jdbc , JSM , WS-* , BPEL or socket enough