Technical Routing Vs Logical Routing

Hi Friends,
Plz differentiale Technical Routing and Logical Routing

Routing
defines how the messages flow via XI (where to, via what) receiver and interface determinations in directory
Logical routing involves the definition of business services/systems for your interface.i.e we difine the flow of messages in a system landscape
Technical routing involves the definition of the communication channels, adapters, etc.
From a general point of view, whenever you talk about logical routing as such, it deals with the security and authentication aspect. By mentioning the business sytems/services for the interface, you are clearly telling, which client and logical system name XI should talk to, to either send or receive data..
.and technical routing involves exactly how the data will be sent or received.
Routing is one of the steps of the pipeline process.
Message was edited by:
Raghavesh Reddy

Similar Messages

Logical and technical routing ?

What is the difference between logical and technical routing ? Technical routing is a pipeline step and can be monitored only in the Integration Engine and is it that logical routing can be monitored only in RWB ?

Hi radhika,
Logical routing determines the logical receiver(s) for a given logical sender.
Logical routing comprises the following two steps:
Receiver determination during which you assign a receiver system to the sender interface of a sender.
Interface determination during which you specify a receiver interface in the receiver system.
Technical Routing is a Processing step of the Integration Engine that determines physical addresses of logical receivers.
The physical address (end point) of the required receiver is retrieved from the Integration Directory.
Both can be monitored in IE(ABAP) - SXMB_MONI.
Thanks,
Shweta

SOAP - XI - RFC. XI not perform Adapter call after Technical Routing.

Hi, All!
I have a problem with XI.
My configuration (all calls are synchronous):
SOAP adapter -> XI mapping -> RFC adapter call to R/3
Most of the time it's works correctlly!
But some times XI does not call outbound RFC adapter after "Technical Routing". And there is no error in XI Monitor, but this XML message marked like "scheduled". So the SOAP adapter returns "Timeout error".
I have compared messages in XI monitor for a successful call and a unsuccessful one. There is no difference in "Routings" and "Mapings" they are the same, except for in the unsuccessful message no "Adapter call" at all!
Do you know how to solve such a problem?
Thank you!!

try to register all queues in SXMB_ADM -> Manage queues.
I think that should help you solve the issue.

Message not processed after technical routing

Hi ,
I have a SOAP ->ABAP Proxy (R/3) scenario that sometimes not processed completely. When checking the message in SXMB_MONI I notice a grey dot (which means log version) in the status column next to the message, Upon opening the message I can't see any errors.
The message has gone through the following steps.
Inbound Message
Receiver Identification
Interface Determination
Message Branch According to Receiver List
Request Message Mapping
Technical Routing
But final stage call adapter not executed so i came to know that response message not reached to XI.
This is occuring once or twice for every 25 to 30 messages.
Can any one provide some suggestions to rectify the above issue.
Thanks & Regards,
Arun.

Check out the below things,
1. Check for which input data it is giving. (Any specific data).
2. This may happen becaus of time out. (Huge data processing)
Also check out below link,
['Log Version' status in 'SXMB_MONI']
Resend the message from sender and it will work properly.
Log version means "Waiting for response" and liable to fail if response not received on time.
Edited by: Siddhesh Pathak on May 13, 2009 12:10 PM

Technical Monitoring for Logical host name

Dear experts,
We are in mid of technical monitoring finalisation.
one of the interesting thing which i found with respect to the logical host name, we installed SMD agent on Virtual host name and our system is not with HA environment and no clustering. It is just a system with single instance.
During the managed system configuration all the physical and logical host name reported by SMD autodiscovery, all went fine. But in Technical monitoring shows only virtual host name with the updated alerts , and logical host name only shows grey alert.
virtual host shows alert here
logical host name shows grey
how can i get alert displayed for logical host name too? do i need to do some settings at the OS level , could you guide us?
Thanks
Jansi

Hi Giri Raju Ayyagari,
I am sorry, seems you are still not able to get my issue, moreover you get diverting my issue
Here the problem is not at all related to agents on fly. thats the separate topic.
We are having issue on Logical Host names where there is no HA environment, means only One logical host name created.
I raised to SAP, l will update once the update from SAP given.
Best regards
Jansi

Logical ethernet interface routing

Is there a way to configure a default route to a logical ethernet interface, another one that isn't of the physical unit? I.e., to have different default routes to hme0 and hme0:1?

Hi radhika,
Logical routing determines the logical receiver(s) for a given logical sender.
Logical routing comprises the following two steps:
Receiver determination during which you assign a receiver system to the sender interface of a sender.
Interface determination during which you specify a receiver interface in the receiver system.
Technical Routing is a Processing step of the Integration Engine that determines physical addresses of logical receivers.
The physical address (end point) of the required receiver is retrieved from the Integration Directory.
Both can be monitored in IE(ABAP) - SXMB_MONI.
Thanks,
Shweta

Hi,about routing

what difference between logical routing and technical routing?
what do both respectively in runtime?

Hi Joy !!
Routing
defines how the messages flow via XI (where to, via what) receiver and interface determinations in directory
Logical routing involves the definition of business services/systems for your interface.i.e we difine the flow of messages in a system landscape
Technical routing involves the definition of the communication channels, adapters, etc.
From a general point of view, whenever you talk about logical routing as such, it deals with the security and authentication aspect. By mentioning the business sytems/services for the interface, you are clearly telling, which client and logical system name XI should talk to, to either send or receive data..
.and technical routing involves exactly how the data will be sent or received.
Routing is one of the steps of the pipeline process.
http://nl.sun.com/companyinfo/nieuws/evenementen/2006/pdf/SunTT-SDN-concepts.pdf
http://help.sap.com/saphelp_erp2005/helpdata/en/a1/e9763c997fda50e10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/2a/d52c413894f823e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/2ffe419625da6fe10000000a1550b0/frameset.htm
Can any one brief me about Routing and Pipiline
Thanks !!
Regards
Abhishek Agrahari

Routing Rules

what is LogicalRouting, TechnicalRouting

Hi Mahesh,
Routing is one of the steps of the pipeline process.
The Integration Engine determines receivers in two steps:
1. Technical receiver information is defined by technical routing.
2. Logical receivers are determined by logical routing.
The logical receiver is separated from the technical receiver, which simplifies the exchange of technical addresses (of an application server, for example) without affecting the logically defined superordinate collaborative process.
1. Technical routing involves the definition of the communication channels, Sender and receiver agreements ,adapters, etc. technical routing involves exactly how the data will be sent or received.
In collaboration agreements, you define the options described in the collaboration profile that are to be valid at runtime for a selection of senders and receivers. For this purpose you select, for instance, for technical routing the communication channel, which is to be active for a group of interfaces (for example, a channel that is intended for all IDoc messages). Collaboration agreements control inbound and outbound processing.
2. Logical routing works on services and is determined by using routing rules: Logical routing involves the definition of business services/systems for your interface.i.e we difine the flow of messages in a system landscape
From a general point of view, whenever you talk about logical routing as such, it deals with the security and authentication aspect. By mentioning the business sytems/services for the interface, you are clearly telling, which client and logical system name XI should talk to, to either send or receive data..
**Pls: Reward with Points if helpful **
Regards,
Jyoti

Routing error for HTTP to JDBC scenarion

Getting following error: please advise.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
<SAP:P1>-BS_POC_TEMP_Sender</SAP:P1>
<SAP:P2>-POC_DB_Temp_Receiver_Channel,http://xys.com/xi/projects/syn/n1.IM_POC_TEMP_DB</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver agreement found for sender -BS_POC_TEMP_Sender to receiver -POC_DB_Temp_Receiver_Channel,http://xys.com/xi/projects/syn/n1.IM_POC_TEMP_DB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hey
Check the URL you have provided the sender system for HTTP.then check if you have configured receiver agreement/receiver determination for that combination of sender and receiver
The messages which is coming in sxmb_moni is unable to find any receiver side configuration for the sender attributes( like sender party/service or sender interface name).
Thanx
Aamir

SMSY Technical System Delete and Clean-up

I need to completely delete a SID from Solution Manager: SMSY technical system, projects, logical components,ChaRM, CCMS, tansport routes, SMD, SLD, etc. I am looking for clean-up documentation. Is there a document(s) which will describe a logical progression to remove an obsolete SID? Logically, removing CCMS and Wily monitoring can occur first. A manual delete of the technical system from the SLD next? Then delete projects and logical components? A good chronological order for steps like these would be very helpful. I'd like to avoid problems with workflow and system batch jobs.

Hi Loenard,
I don't think there is any job or program to do this. Best thing to do is if your system to be deleted is still running and is still sending data to solman SLD from RZ70 then disable this by removing the hostname data and save it. this isolates the system to be removed. next in SMSY, remove system from the product landscape from "logical components" list and then you can remove the system from product systems under "landscape components". here you may need reload the product landscape in solution landscape if it doesn't go away itself. if it gives issues then you can use the "where used" button and that tells you where it is still assigned and remove it from there.
hope this helps

Who are the logical receivers

i couldn't understand who are the logical receivers after reading help.sap. please take one example and tell the importance of logical receivers.
Thank you

Hi Ajay,
Logical routing involves the definition of business services/systems for your interface.
Technical routing involves the definition of the communication channels, adapters, etc.
From a general point of view, whenever you talk about logical routing as such, it deals with the security and authentication aspect. By mentioning the business sytems/services for the interface, you are clearly telling, which client and logical system name XI should talk to, to either send or receive data...and technical routing involves exactly how the data will be sent or received.
Regards,
Sushumna

Logical System Name Not appearing in the Business System

Hi,
Initially we had created a Technical system with Client 700 without a "Logical System Name" in SLD. hence the 'logical system name' in 'business system' was also Blank.
Now, since we are implementing the IDOC to file scenario; we need to maintain the "Logical System Name" in the client and which in turn should reflect in our Business System in SLD.
Though we maintained the Logical System Name in the Technical System --> Client --> Logical System Name; we are unable to see the same(Logical System Name) in Business System ('Integration' tab)
Please also note that Business System is of the ROLE: Integration server.
When we go to business system in SLD ---Integrtaion tab ---Logical System Name -- is still blank.
Can anyone please help us to update the 'Logical system name' in Business System in SLD?
Regards,
Rehan

Hi Sunil,
I followed your link till
Bussiness System -> select your bussiness System -> in Below pane u will find Details of your bussiness system ->amongs the various tabs available select Integration Tab->U will See option for technical system beside that u will see option for change ->click this ->u will be taken to Logical system ->there u define u r logical syatem name and then save the entries.
When I clicked the option chnage ---> "Change Associated Technical System" appeared, It didn't take me to Logical system.
But in turn I clicked hyperlink corresponding to Technical systems, it took me to technical system --> clients tab --I have entered the Logical system name.
When I go back to Business system again its not showing the Logical system name in Integration tab.
regards,
rehan

Logical System not appearing in SLD

Hello Friends,
Logical System of SAP R/3 system is not appearing in SLD. The logical system is available in backend ABAP System. I have even run the RZ70 data collection programs as well. However, I am not able to populate the logical system names in SLD.
I have put the same logical system names in the client tab of the technical system but in vain. The logical system field is non-editable and I believe it is always non-editable unless some technical system is not assigned to it.
The logical system name is also not available in ID (if it is not in SLD then it won't be in ID as well).
[The SLDCHECK is throwing exception 4. what to do for this? May be the data is not transfered because of this? Even though I have maintained proper password in SLDAPICUST!!!]
Request your kind adivse on what can be done. Where can I lookout for possible errors.
Thanks & Regards,
Anand Patil

Hi
On SLD - > Technical System -> Client -> Logical System Name , generally It is Editable entity .
If in Your Case , You can not change it, chech with ut basis Guy , for roles and authorisation against your Username ,
Check the Same SLD Roles with some PI Service User.
Regards
Prabhat Sharma.

Logical file name or logical path name incorrectly defined

Dear All,
We are doing archival in our IDES for test purpose before we do it to our Production.
Steps Performed
Copied AM_ASSET archive object to ZAM_ASSET
Logical Path
Logical path ZAM_ASSET
Name Asset
Syntax group UNIX Unix compatible
Physical path /archive/test/<FILENAME>
Logical File Name
 Logical file ZAMASSET
 Name Asset
 Physical file FI_<MONTH>_<DAY>.txt
 Data format ASC
 Applicat.area AM
 Logical path ZAM_ASSET
But when we run the WRITE though SARA , in the job log we get the following
Logical file name or logical path name incorrectly defined
When generating a file name for an archive file that is to be created, the system determined that the logical file name FIAA_ARCHIVE_DATA_FILE or the logical path name ARCHIVE_GLOBAL_PATH was defined incorrectly.
But we have maintained a Logical name ZAMASSET , so we are unable to change the location of archived file and as well as the format.
So is there any setting we need to maintain apart from the logical file name and logical file path.
Suggestions are highly appreciated.
Thanks in anticipation

hi,
follow this steps :
- transaction SARA
- enter authorization objects, eg SD_VBAK
- hit button CUSTOMIZING
- Archiving Object-Specific Customizing: execute Technical Setting
- field Logical File Name enter or select ARCHIVE_DATA_FILE
- leave CONTENT REPOSITORY as blank if you are not using 3rd party for storing (eg. IBM Tivoli)
- back to customizing
- from Basis Customizing, execute : Cross-Client File Names/Paths
- on Logical FIle Path Definition, highlight (select) ARCHIVE_GLOBAL_PATH on the right pane
- double click on the Assignment of Physical Paths to Logical Path on the left pane
- double click on OS used, eg. UNIX, define Physical Path where archive file (on WRITE process) will be stored
- save changes made
- double click Logical File Definition, Cross Client on the left pane
- double click ARCHIVE_DATA_FILE on the right pane
- make sure that logical path is already set to ARCHIVE_GLOBAL_PATH
- save changes made
this setting also can be done using transaction FILE
we have experienced on this case using SAP standard archiving (SARA, SARI) and everything is fine with this setting above.
hope it help you.
rgds,
Alfonsus Guritno

How to change logical system name

hi,
there is no logical system name for business system in sld on integration tab.
this bus sys is based on tech sys which is configured as integration server.
plz tell me how to give the logical sys name there.
plz reply me it is urgent.
vijender

Jochen Gugel wrote:
> Hi @ll;
>
> at the tab in technical system the logical system name was correct.
> But it wasn´t shown at the integration tab of the business system.
> I solved this problem by deselecting the integration server, save this settings and reselect it afterwards.
>
> Kind regards
> Jochen
hello all,
I'm actually having the same issue. This issue is NOT the popular adapter-specific identifier problem where the business system in the ID needs to be compared with the SLD. This issue is that the within the SLD on PI 7.0 the Logical System Name of a given business system is not present although the logical system name of the specified technical system does appear. You cannot change the LSN of the business system since it relies completely on the LSN of the associated technical system.
I used Jochen's approach before and it worked, but i've tried this again since i'm having the same issue. Only now it doesn't work.
i solved this issue by deleting the old BS and recreating it
Thanks,
Edited by: Jason Ray on Jun 24, 2008 5:47 PM

Technical Routing Vs Logical Routing

Similar Messages

Maybe you are looking for