What’s in a Naming Convention?
It doesn’t take long for a PI implementation to become a complete mess if standards are not put in place before development occurs. Even among seasoned developers, opinions vary as to the best way to name and organize the IR (ESR) or ID (IB), depending on different backgrounds and previous project experience. In the next few blogs I would like to touch upon some of the best practices that we utilize in our implementations at DataXstream, which we have arrived at though our project experiences and discussion, both internally and with other middleware experts. Read more
Troubleshooting the Services Registry
Recently I set up the services registry for PI 7.1 EHP1 for a client of ours. Although it seemed like it would be a simple process, I ran into a 401 authorization issue and another issue where web services were not publishing to the services registry. Looking online there are a lot of people who ran into the same issues as I did, so I am providing, here, the steps to perform if your services registry isn’t working.
Changed RFC Structure Not Propagating to XI/PI Runtime
In support of an synchronous XI interface (SOAP->XI->RFC), I changed the underlying structure of one of the RFC parameters. I appended some fields to the end of a return structure in ECC. I re-imported the RFC meta data to the Integration Repository as always and mapped the fields accordingly. When I executed the interface, the fields that I added did NOT appear in the XML. This is because the XI runtime cache did not have the updated metadata for the RFC.
To update the runtime cache (called CPA Cache), enter the following URL in your web browser http://<host>:5<sys#>00/CPACache/refresh?mode=full. XI will do the rest of the work for you. After the CPA cache is refreshed, the new RFC meta data reflects the newly added fields.
These other CPA Cache URLs may also be helpful:
CPA Cache Monitoring: http://<host>:5<sys#>00/CPACache
Delta CPA Cache Refresh: http://<host>:5<sys#>00/CPACache/refresh?mode=delta
Full CPA Cache Refresh: http://<host>:5<sys#>00/CPACache/refresh?mode=full
Allow Additional Mapping Types in SAP XI/PI
SAP PI is a powerful integration engine that allows developers a variety of methods for implementing transformation logic. As a long-time ABAP developer, one of my favorite methods to implement transformation logic is using ABAP. This transformation option is not enabled in SAP XI/PI out of the box. While information regarding how to enable ABAP transformations can be found in SAP help, I have found it easier to have step-by-step instructions.
SAP Exchange Infrastructure – JMS for Oracle AQ Setup Instructions
By: Timothy Yates and Wess Tobler
Description:
This document gives step-by-step instructions on how to install, setup, and configure the JMS adapter to communicate with Oracle AQ Messaging. Oracle AQ and the SAP XI adapter are not compatible as delivered by SAP and Oracle.
DataXstream adapter software was developed to bridge the incompatibilities between the SAP JMS adapter and Oracle AQ.
SAP Exchange Infrastructure – JMS for Oracle AQ Setup Instructions
DataXstream Can Integrate Anything To SAP – Even A Toaster!
Why would you integrate a toaster with SAP?
SAP integration is our specialty. We figure that if we can integrate SAP to a toaster, we can integrate SAP to anything! From shop floor-automation, warehouse automation, accounts receivable, human resource management systems and, well, toasters, DataXstream is the leader in SAP integration.
How do you integrate a toaster with SAP?
How did we integrate SAP to a toaster? First, we created a custom ABAP application on our SAP R/3 4.7 Enterprise application server. This custom program calls a RFC on our SAP Netweaver Exchange Infrastructure 3.0 (XI) server. The XI server converts the RFC call into a web service XML message. The web service message is sent to a custom web service application implemented on Microsoft IIS 6.0. The web service application receives the XML message and uses a .NET DLL to communicate with a programable logic contrller (PLC) server. The PLC server communicates with a PLC that controls a stepper motor. The stepper motor is attached to the handle of the toaster. The handle is lowered to start the toaster and raised when the appropriate amount of time has elapsed. In addition to the SAP integration, DataXstream resources handled every step of the process including .NET programming and hardware fabrication.
 |
 |
