Queue registration

What is queue registration ?? Why we do queue registration ??
thanks
kumar

Kumar,
Yes exactly , XI comes with queues. But why we need to De-register and register the queues? I can't suggest you the real time example/purpose of doing this. Since I haven't did this.But I can tell you the functioanlity of it.
Consider you are seeing lot of LUW recorded in outbound queues, most of them were errored out due to some communication failur or some other reason, u want to execute them individually , but at the same time u are getting lot of messages from Inboun queue also. So wht we can do , we can De-register the Inbound queue and process all the Outbound queues. Again we can register the Inbound queues so that it wil start its flow, is it confusing?
Ok Let me figure out with diag
Inbound Queue -
>XI Integration Server -
>Outbound Queue.
-- you want to process the Outbound queue as per my above example, so de-register the Inbound Queue.
-- Now you processed the Outbound queue , so Register the Inbound queue to flow as normal.
-- What happens ,if you de-register the inbound queue? Don't worry nothing will be error out, everything will wait in the queue. You can check the same in SMQ1.
I hope it clears u lil bit!!!!
Best regards,
raj.

Similar Messages

Question on MAXTIME parameter on queue registration

Hi
I have a question regarding value of parameter MAXTIME - while registering for queues in XI . My intention is to prioritize queues - XBTA, XBTG, XBTZ with the *A queue having the maximum priority and the *Z having the least. Should I give a high value in seconds for the *A and a least value for *Z queue ? I read the definition of MAXTIME - as <b>'The MAXTIME parameter determines the time in seconds that is scheduled for processing a queue'</b> .
So, based on the above definition , should we give a higher value of MAZTIME for queues with higher priority - could somebody elaborate ?

Hi KARTHIK MATHRUBOOTHAM ,
These r the details Queues Prioritization:
Queues for Prioritized Message Processing
http://help.sap.com/saphelp_nw04/helpdata/en/04/827440c36ed562e10000000a155106/content.htm
Queue prioritization for XI processing queues uses a built in feature of qRFC. By specifying the maximum processing time for a queue, u can define how much processing time a specific queue will get(this works like a time-scheduling procedure, time slicing). U can use this feature to add queues for high-priority and low-priority messages(for inbound and outbound processing). These queues are then named, for example XBT1* or XBT9* for inbound EO processing and XBTA, XBTZ for outbound EO processing.
This function uses the message filter concept and can be configured in transaction SXMB_ADM. U can define message filters for specific message attributes such as sender/reciever service, interface and so on. A filter can also be dependent on the message size.
This function can also be useful in situations where a queue backlog needs to be processed, due to a system error or an error on the reciever side, for example. In this case, u can use a Prioritized queue for urgent messages that must be processed immediately, without having to process the whole back-log first.
How to prioritize XI messages on the integration server
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
The parameter QualityOfService specifies how the Integration Engine should process a message. The following values are permitted:
1)BE(Best Effort: synchronous processing). If QualityOfService is BE, the client is sent the final status for the processing.
2)EO(Exactly Once: asynchronous processing with guaranteed execution exactly once). If QualityOfService is EO,processing occurs asynchronously and the client only recieves a confirmation of reciept with HTTP status '200'.
3)EOIO(Exactly Once in Order: asynchronous processing using queues, that is, guaranteed execution exactly once and maintaining the sequence of successive messages). If QualityOfService is EOIO,processing occurs asynchronously and the client only recieves a confirmation of reciept with HTTP status '200'.
Since u had choosen EOIO ,You must also define a queue name for EOIO:
XI.QueueId=<QueueName>
This queue name is used in the Integration Engine to process messages in the same sequence that they arrived in.
This QueueName can consist of a maximum of 16 characters. If the first 8 characters contain 'SAP_ALE_', these r removed since this value is reserved by SAP and used internally.
If a value is not specified for QualityOfService , the default value 'BE' is used.
These r following websites which u wil find helpful:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
http://documentation.softwareag.com/crossvision/xie311/admin/config.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca52244
cheers!
gyanaraj
****Pls reward points if u find this helpful

CRM list of queues registration information

Hi,
I am new to CRM and have some questions regarding BDocs and queues in CRM,
1. We found some queues starting with CSA* in inbound getting stuck for long. Found the reason to be that since these queues are not registered, they are not processed. Do these BDocs really need to be processed? 2. If yes then what all queue names are to be registered in CRM. What each of these inbound queues does?
3. If not needed, then how can we delete these queues?
4. Any step - by step document for registering Queues or on BDocs?
Point to note is data is transfered from CRM to BW.
Appreciate your help...
Regards,
Madhav

>
Kai Blanke wrote:
> As I said: As long as the CSA queues exist, there will still be BDocs in the MW in an intermediate / yellow state, as the CSA queues are used for internal asynchronous storing of BDocs during processing. If you delete the queues, you will need to delete the BDocs also, and eventually get data inconsistencies depending on where you distribute your data. If you are deleting them, your MW will get stuck with hanging BDocs which is not an alternative.
> Therefore you should register the queues and have the entries processed. As these are processed internally, the processing is pretty fast; a nice server should process some tenthousands per hour.
>
> The only way of not generating such queues is by stopping the MW, but this is only an option for a standalone system.
We also have the same problem. The CSA* queues are not registered in SMQR. We have queues dating back to May of 2008. Will it be safe to delete them? Or should we still process these queues? We have 51,000++ messages on the inbound queue right now. Any help on this will be very much appreciated. Thanks!

How to create the Queues

Please find the below scenarios
1) R/3(A system ) -
>Client PI--->Server PI---->File1
2) R/3(B system) -
>Client PI--->Server PI---->File2
In the above scenario the data transfer between through HTTS soap communications. While receiving the data at Server PI end, we have used the QOS=EOIO and we have used the Queue XBQI_22. This Queue has been used for the First scenario.
Here my doubt is, shall i use the same Queue for the 2nd scenario also? If I can, who will create the Queues( means Queues will be created by PI Developer or Basis Person).
If possible plz provide me the steps, how to create the Queues.
Thanks in advance,
Regards,
AVR

Hi AV,
Go thru following blogs....it will help you to play around with queues...
XI Asynchronous Message Processing: Understanding XI Queues -Part I
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
How To Prioritize XI Messages on the Integration server
IN this u will come to know how to priortize message using the Queus.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc1869733413
Also have a look on the following link...
queue registration
With Regards,
Pinangshuk.

CNS Transport Failing to Send Registration?

I have a nearly fresh install of Solaris 10 8/07. This is my first foray into the Solaris OS so bear with me if I'm making a dummy mistake. I signed up for a year of support and have entered my credentials through updatemanager and have been successfully downloading and installing patches for weeks now. The problem I am having is that my logs are filled on a daily basis with the following message:
Apr 21 08:53:30 mercury.transware.net CNS Transport[14830]: [ID 617356 daemon.error] Could not send message from queue: /var/tmp/cc-transport/CCTQueueStore/store/queues/REGISTRATION/registrationI can't seem to find any resolution to this by googling it.

Applying patch 12108[1|2]-08 (that is sparc) should resolve the problem for you. The error that you are getting is as a result of the recent decommission of the Sun UC Portal.
If this does not resolve the issue for you, please run the following commands:
# /etc/init.d/cc-transport stop
# /usr/lib/cc-cfw/framework/lib/cc-client-adm stop
# /usr/lib/cc-cfw/framework/lib/cc-client-adm disable
# rm -rf /var/tmp/cc-transport/*

In Bound and Out Bound Queues

Hello All,
Can some body explain what is meant by a Queue.
Why do we require queues to transfer the the data
In our land Scape we have XI through XI messages(Pay load) are transfered
My question is Now a days many of the customers implementing XI
So do we require Queue registration
If Yes please explain me breifly.
Thanks &Regards,
Praveen Kondabal.

Hi Praveen,
XI messages for inbound processing are placed in inbound queues of Integration Engine and placing them in outbound queues carries out outbound processing. As a part of Integration Engine configuration, we register XI queues. By registering queues used by the Integration Engine, we intimate qRFC the technical names of these queues
Do refer these ~
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
/people/vasanthakumar.balasubramani2/blog/2005/12/21/complete-reference-for-idoc-queuing-and-monitoring
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
Regards,
Madhu

PI - Queues

hi Experts,
I have very basic question for my clarification,
What's the diffirences between SXMS_QREG Queues and SMQR.
I understand SXMS_QREG where you have all the queues for EO, EOIO and BE but then how about SMQR queues what are they? when we use?
Please help me to understand.
Thanks
Sekhar

Hi Sekhar,
To enable messages to be processed with a higher or lower priority in the corresponding queues, you must register the queue prefixes XBTA, XBTZ, XBT1, XBT9, XBTX, and XBTY in transaction SMQR beforehand. Proceed exactly as you did when registering the other queue prefixes (XBTI, XBTO, and so on).
During queue registration, you are asked to provide a value for the MAXTIME parameter. This parameter enables you to assign priorities for queue processing using the queue prefixes.
The MAXTIME parameter determines the time in seconds that is scheduled for processing a queue. By varying this time, you can use the queues with prefixes XBT1, XBTI, und XBT9 as queues for messages with high, medium, and low priority, for example. The same applies to the queues with prefixes XBTA, XBTO, and XBTZ. In this way, you can put messages from different application cases in different queues, and use the prefix of these queues to determine the priority of message processing.
http://help.sap.com/saphelp_nw04/helpdata/en/04/827440c36ed562e10000000a155106/frameset.htm
More on queues;
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
- How to Re-Process failed XI Messages Automatically
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
- Understanding XI Queues
Regards,
Divya

SMQ2 Time limit exceeded

Hi Experts,
IDOC to IDOC Scenarion--There are some entries in SMQ2 are showing "time limit exceeded". i tried to unlok the Queue every time i get the error and after that queue is going into Running status for some time and again it is giving the same error and status is "SYSFAIL". Queue registration is also done.we are facing this problem in production.
All other interfaces messages are processing fine except for one interface. some IDocs are processed even for the same interface. I assumed that the size of the message is large. so it is not processing, mapping step is not executed.
see the example below for one message which is not processed from XI
<SAP:MessageSizePayload>467228</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>479041</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>467228</SAP:PayloadSizeRequest>
We have restarted the complete XI server after Kernal upgrade and after that we are getting this problem, can any body give me the suggestion how can we solve the problem.

Hi
The size of the messages also not huge, we have tested it testing system and it is taking less than one minute to process the message. And we have checked at the Gate way & JCO connections are working fine. The problem is still there as i explained in my first post.
Every time it is giving time limit exceeded after unlocking the Queue.
Is there any other suggestions to resolve this issue.
Thanks in Advance
Neeru
Edited by: neeru on Mar 3, 2010 2:57 PM

Scheduled for Outbound Processing

Hi,
I have a simple problem: I want to send a XML file from a place to another place. When I put the file in the sender folder, XI import this file correctly, therefore, the file doesn't go to the receiver folder.
In the XML monitor, the current status (message lifecycle) is "Scheduled for Outbound Processing".
What can be happening?
Tks,
Douglas

Hello Douglas,
I think that message is sitting in the queue. May be you should check whether queue registrations are done already. Otherwise the message might sit in the outbound queue. You can goto the queue entry (from monitoring) and unlock it if this is the case.
Regards
Rampi.

Solaris 10 x86 SunUpdateManager errors: Can't open default CCR

I have a V20z running Solaris 10 (6/06 I believe) which has been registered successfully
with the Sun Update Connection and it has, until recently, been getting and applying
patches successfully.
After the last set of patches was applied (involving a reboot), the machine has taken to
generating an error message which confuses me .
The machine is continually saying:
CNS Transport[3135]: Can't open default CCR. Be sure you are running as root.
CNS Transport[3135]: Could not send message from queue: /var/tmp/cc-transport/CCTQueueStore/store/queues/REGISTRATION/registration
Could someone please tell me what on earth could have gone wrong for this to start
happening?
David Wiseman/David Martin
UWO Computer Science

The transport is used for the optional web feature of the SunUC software. The errors you are getting could suggest a number of problems from a failure to connect to a malformed entry in the queuestore.
In the first instance i'd verify that the transport can connect -
# /usr/lib/cc-cfw/platform/transport/bin/cctrunner -p
Then review the error logs (if they exist) -
* /var/log/swupas/swupas.log
* /var/log/swupas/swupas.error.log
And if they show no problem i'd clear the existing queuestore to ensure there are no problems -
# /etc/init.d/cctransport stop
# rm -rf /var/tmp/cc-transport/*
# /etc/init.d/cctransport start
And then re-test the cctransport process can connect ok -
# /usr/lib/cc-cfw/platform/transport/bin/cctrunner -p

Scheduled for oubound processing

Hello,
I have a simple szenarion (fileAdapter->XI->fileAdapter). I've done all the nessesary work in IR and ID and put a xml-file in the InDir of the file adapter.
I can see the message in the monitor but it get the status "Stop" with the icon "Scheduled for oubound processing". Now error is displayed as you can see in the attached trace.
Any idea what I can do ?
Regards Bernd
Message was edited by: Bernd Schloemer

Hi
I think that message is sitting in the queue. May be you should check whether queue registrations are done already. Otherwise the message might sit in the outbound queue. You can goto the queue entry (from monitoring) and unlock it if this is the case.
Regards
Arpit Seth

Many entries in DBA_SUBSCR_REGISTRATIONS

We use Advanced Queueing-Feature for Forms "External Events". We use RDBMS 11.2.0.2 EE-RAC.
During the last days we had increasing problems with the performance of the database.
We try to assess, whehter AQ was the reason for the problem.
We had a lot of Session waits "library cache lock". We saw a lot of Statements for reg$-table.
In the table DBA_SUBSCR_REGISTRATIONS were 114000 entries.
Is it posible that the performance degrades when a lot of queue-registrations are available (a lot of enries in DBA_SUBSCR_REGISTRATIONS)?
Is it possible to clear (remove all at once) the registrations without restarting the instance?

We use Advanced Queueing-Feature for Forms "External Events". We use RDBMS 11.2.0.2 EE-RAC.
During the last days we had increasing problems with the performance of the database.
We try to assess, whehter AQ was the reason for the problem.
We had a lot of Session waits "library cache lock". We saw a lot of Statements for reg$-table.
In the table DBA_SUBSCR_REGISTRATIONS were 114000 entries.
Is it posible that the performance degrades when a lot of queue-registrations are available (a lot of enries in DBA_SUBSCR_REGISTRATIONS)?
Is it possible to clear (remove all at once) the registrations without restarting the instance?

Connection Object Delta Load not happening

Hi Gurus,
             I am doing integration between ISU and CRM 5.0. I have achieved integration both sides for BP , Contract Account. I have also done initial load for Connection Objects using object 'SI_CONNOBJ'. We are able to see IBase getting created for the Connection Objects but when I change the data in a particular Connection Object it is not trigerring Delta Load for the Object.
            Please help me for the same.

Hi Aishuman,,
Please check for the following entry in R/3 table TBE31:
EVENT    IBSSICON
LAND
APPLK    BC-MID
FUNCT    ECRM_CONTRACT_COLLECT_DATA
which brings the delta change to CRM.
Also,in CRM txn:R3AC1,check for the filter setting for object SI_CONNOBJ.
Also,in R/3 table CRMRFCPAR ,make sure that for object SI_CONNOBJ(or *) for consumser CRM(or *),value of DISCARDDAT is not set to X.If set to X,would prevent delta change to flow to CRM.
Also,check for the queue registration in txn:SMQR.If your queue is de-registered or lock is set,then entry will not be processed in CRM.
Hope this helps!
Regards,
Shanthala Kudva.

What's the mean of error infomation ?

tail /var/adm/messages
it shows as follows
Feb 4 09:32:44 mail3 last message repeated 1 time
Feb 4 09:34:45 mail3 SRS Proxy[1397]: [ID 663108 daemon.error] Could not upload bulk message
Feb 4 09:34:47 mail3 SRS Proxy[1397]: [ID 388765 daemon.error] Could not send message from queue: /var/SUNWsrspx/SRSQueueStore/store/queues/REGISTRATION/registration
Please tell me what's the mean?? thank you !!

One more time:
This appears to be some kind of Sendmail error, not an iMS error. First, iMS does not normally log anything to /var/adm, so errors you see there are very unlikely to be from Messaging Server.
Second, none of us here really is likely to know sendmail well.
I would first check that you haven't installed some patch that has restored sendmail. Normally, on install of iMS, we replace Sendmail with our "compatibility" binary. Patching can replace that with real Sendmail, and your startup scripts can start Sendmail, preventing iMS from fully starting. Please check that.
If you believe that this is an error coming from iMS, then you will need to provide some context, like where the message shows, and any other symptoms. This bare error message doesn't really allow me to help you,.

BDocs in intermediate state.

Hi All,
While making delta changes to business partners I find that the BDoc's are going into an intermediate state. When I check the Inbound queue in CRM the queues seem to get into a 'READY' status, if I unlock these entries in smq1, or if i reprocess the BDOC, things are working fine. However the delta changes are not taking place automatically.
I have checked the queue registration, the following queues have been registered CRI, CIR, CRM_BUPA, CSA, R3A, AND R3U. I find that the status of queue demon in t-code smohqueue is Running. However I find that in most systems where the delta changes are taking place automatically, the status is released, and not running. What should the correct status be?
If i click on start queue demon, it goes into running status, and i am unable to change it to released status.
Kindly request your help in analyzing why the delta changes are going into intermediate state.
Regards,
Thiru

I have the same problem. Did you solve?
Regards,
Lyda

Queue registration

Similar Messages

Maybe you are looking for