on 08-10-2009 7:18 AM
Hi,
PI 7.1 Best Practices: Naming Conventions:
https://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/40a66d0e-fe5e-2c10-8a85-e418b59ab36a
the earlier one was few years old one (recommended until PI 7.0):
seems the major changes are in naming guidelines for Service Interfaces and Service Operations.
service operation name not recommended to be the same as service interface name.
let me know if you notice any more changes, do share.
thanks,
Jagdishwar.
thanks for the doc.
regarding communication channel naming there are few changes:
xi 3.0 recommendations:
Communication Channels Naming
For Sender: <Service>_<Message Type>_<Adapter Type>_Server
For Receiver: (Ack_)<Service>_<Message Type>_<Adapter Type>_Client
examples: Sys_PRD_810_IDoc_Client Sys_XR3_100_RFC_Client Sys_PMyCompHRPayMaster_Payroll_JDBC_Server
PI 7.1 recommendations
Communication Channels Naming
(Ack_)?<Adapter Type><Direction><Object | Description>?
Glossary
<Adapter Type> : IDoc | RFC | File | JDBC | JMS | Proxy | SOAP | Http | Mail | RNIF | <Other>
<Direction> : Sender | Receiver
<Object> : Specify an underlying business object or message type
<Description> : Describe the usage of the channel
examples: IDocReceiver FileSenderProduct SOAPReceiverQuotation MailReceiverQuotation
I think the newer one pi 7.1 recommendation is much more easier to interpret and straight forward.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.