General¶
This manual describes how to use SAP as the Insight EAM.
There are serveral alternatives for the connection:
- Connect with SAP Java Connector (JCo) as client (RFMs) and Server (IDocs)
- Connect with Web Service as client to SAP PI/PO
- Connect with Web Service as client to SAP NetWeaver Application Server
The integration can be done on the base of the following technologies:
- WildFly Application Server (Java EE)
- Apache TomEE (Java EE)
Sap Connector¶
- For the communication between Insight and SAP PM, a SAP connector is used, which is based on the version "SAP JCo Standalone Version 3.0"
see https://support.sap.com/en/product/connectors/jco.html
WildFly Application Server (Java EE)¶
- If connection with SAP Java Connector (JCo):
-
unzip gis-sap-modules.zip to x:\GIS\insight\wildfly\modules\
.\wildfly\modules\com\sap\conn\jco\main\insight-sap-connector-api.jar .\wildfly\modules\com\sap\conn\jco\main\module.xml .\wildfly\modules\com\sap\conn\jco\main\sapjco3.jar .\wildfly\modules\com\sap\conn\jco\main\sapjco3.dll (Windows) .\wildfly\modules\com\sap\conn\jco\main\libsapjco3.so (Linux)
-
Copy insight-sap-connector-ra.war into x:\GIS\Insight\Wildfly\standalone\deployments
- Copy insight-sap-web.war (v2-Server) into x:\GIS\Insight\Wildfly\standalone\deployments
- Copy insight-sap-adapter.war (v3-Server) into x:\GIS\Insight\Wildfly\standalone\deployments
- If connection with SAP Java Connector (JCo) as server (IDoc)
- Copy insight-sap-jcoserver.war into x:\GIS\Insight\Wildfly\standalone\deployments
- Copy insight-sap-idoc.war into x:\GIS\Insight\Wildfly\standalone\deployments
- Configure SAP logging
- Logging files: .\Wildfly\standalone\log\insight-sap.log
- Configuration: .\WildFly\standalone\configuration\standalone.xml
<profile>
<subsystem xmlns="urn:jboss:domain:logging:3.0">
...
<size-rotating-file-handler name="INSIGHT-SAP" autoflush="true">
<formatter>
<named-formatter name="PATTERN"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="insight-sap.log"/>
<rotate-size value="10m"/>
<max-backup-index value="10"/>
<append value="true"/>
</size-rotating-file-handler>
<logger category="gis.insight.sap" use-parent-handlers="false">
<level name="DEBUG"/>
<handlers>
<handler name="INSIGHT-SAP"/>
</handlers>
</logger>
...
</subsystem>
Apache TomEE (JavaEE)¶
- If connection with SAP Java Connector (JCo)
- Copy JCo files to TOMEE/lib/sap
TOMEE/lib/sap/insight-sap-connector-api.jar
TOMEE/lib/sap/sapjco3.jar
TOMEE/lib/sap/sapjco3.dll (Windows)
TOMEE/lib/sap/libsapjco3.so (Linux)
- Copy insight-sap-connector-ra.war into TOMEE/webapps
- Copy insight-sap-connector-ra.war into TOMEE/webapps
- If connection with SAP Java Connector (JCo) as server (IDoc)
- Copy insight-sap-jcoserver.war into TOMEE/webapps
- Copy insight-sap-idoc.war into TOMEE/webapps
- Configure TOMEE/conf/tomee.xml
<Deployments file=„<TOMEE-PATH>/webapps/insight-sap-connector-ra.rar" />
- Configure TOMEE/conf/catalina.properties
common.loader=...,"${catalina.home}/lib/sap/*.jar“,...
-
Configure TOMEE/conf/context.xml
<!-- bei WebSEAL wurde nur eine JSESSIONID an den Client ausgeliefert -->
<!-- Insight braucht eine für Maximo und eine für die Insight-Middleware -->
<Context sessionCookieName="INSIGHTJSESSIONID">