David,
Allow me to clear up a few of your points.
1. MII to XI - Supporting SAP XI in SAP xMII 11.5 - Is there a similar document available for xMII 12.0?
**These add-on action blocks are now built-in with version 12.0, so the combination of the PDF guide and the 12.0 help docs should help.
3. MII Queueing Action Blocks
**File system (11.5), and NW DB (12.0) based but not likely what you want in this case.
4. MII Web Service XI Action Block
**Built-in with 12.0, check the help docs for more info.
If MII is distributed at your plants, and ECC is centralized at your corporate location, what about XI / PI, is this also centrally located?
Not to add more wrinkles to this, but the JRA action blocks in 12.0 also provide some outgoing (from MII to ECC) retry capabilities, similar to the 'set it and forget it' approach that you would have with an outbound request going from MII to XI.
Many customers tend to use a relational database to handle the outgoing buffers to provide the disconnected operation support you are looking to accomplish. Once the xml payload has been delivered to XI you no longer have the ability to tweak any values that may have been entered incorrectly (sort of a one way process), but customers using to choose the database approach to outgoing buffering also have an opportunity for supervisor/admin users to review or correct/retry the requests.
As you have already observed, MII provides you with plenty of choices and flexibility in this arena, but the typical 'best practice' recommended approach would be to match up your needs with the environment. If you learn the technical ins and outs of these options, it might become very evident as to the right approach.
Regards,
Jeremy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.