This blog provides basic technical comparison between IBM Sterling & SAP PI.
Both middle-ware are good for EDI interfacing.
| IBM Sterling | SAP PI | |
| Architecture | SI is designed for EDI | PI is designed for EDI and non EDI interfaces.Specially when it comes to SAP interfacing. |
| Mapping | Debugging is not easy | We can debug mapping on field by field by checking queue |
| Context handling done using index.In case of complex mapping Indexing will double demension array | Context Handling seems easy | |
| We have to right all codes | Most cases standard and graphical mapping codes are generated automatically | |
| In case XSD changes we don’t have a option of reimporting the XSD in existing map | This can be done and if root node is not changed Mapping can be retained | |
| Connection | Connecting different partner is easy to connect and maintain using Envelope | We need to create different connection for each partner unless using TPM functionality |
| Access | If user has access to see any particular object he will automatically have access to change – Bug | different Roles can be used |
| Admin | Transport are mostly file based | File and CTS+ |
| Transport can be done from command and GUI import/Export both are file based | More controlled and version management is really good |