Dedicated queue in EO

Hi,
For one of our SOAP - XI adapter interface which has QoS as "EO" , we would like to have a dedicated queue for this interface only.
Where can this be defined? 
Appreciate your input.
Many thanks,
Dharmi

Rajesh,
Thank you for your reply. I know for EOIO you set the queues in Sender channels.
Those EOIO queues block the EO messages and that is the problem. Kindly let me know how the priority queues can be set?
Regards,
Dharmi

Similar Messages

  • IDOC TO XI WITH DEDICATED QUEUE HAS STATUS 30

    Hi,  i have an interface IDOC to XI to JDBC, it has implemented a dedicated Queue, it dosnt have configured the acknowledge.
    it was working fine, then we implemented the dedicated queue, it works fine a cuple of thays but then the idocs start to have all status 30. (note: i have configured output mode 2)
    SM59 config image:
    <a href="http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG">[IMG]http://img144.imagevenue.com/loc991/th_95044_SM59_122_991lo.JPG[/IMG]</a>
    or:
    <a href="http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG">[img=http://img144.imagevenue.com/loc991/th_95044_SM59_122_991lo.JPG]</a>
    WE20 config image:
    <a href="http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG">[IMG]http://img169.imagevenue.com/loc768/th_95050_WE20_122_768lo.JPG[/IMG]</a>
    or:
    <a href="http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG">[img=http://img169.imagevenue.com/loc768/th_95050_WE20_122_768lo.JPG]</a>
    Table IDXQUEUE in XI SE16 image:
    <a href="http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG">[IMG]http://img140.imagevenue.com/loc850/th_95050_XI_SE16_IDXQUEUE_122_850lo.JPG[/IMG]</a>
    or:
    <a href="http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG">[img=http://img140.imagevenue.com/loc850/th_95050_XI_SE16_IDXQUEUE_122_850lo.JPG]</a>
    Function module in SE80 image:
    <a href="http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG">[IMG]
    http://img41.imagevenue.com/loc768/th_95052_SE80_FM_122_768lo.JPG[/IMG]</a>
    or:
    <a href="http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG">[img=http://img41.imagevenue.com/loc768/th_95052_SE80_FM_122_768lo.JPG]</a>
    First message that came out by de dedicated queue image:
    <a href="http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG">[IMG]http://img179.imagevenue.com/loc193/th_95057_first_message_122_193lo.JPG[/IMG]</a>
    or:
    <a href="http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG">[img=http://img179.imagevenue.com/loc193/th_95057_first_message_122_193lo.JPG]</a>
    Last message that came out by de dedicated queue image:
    <a href="http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG">[IMG]http://img192.imagevenue.com/loc343/th_96230_last_message_ok_122_343lo.JPG[/IMG]</a>
    or:
    <a href="http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG">[img=http://img192.imagevenue.com/loc343/th_96230_last_message_ok_122_343lo.JPG]</a>
    BD87 from the day that everything work fine to today image:
    <a href="http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG">[IMG]http://img178.imagevenue.com/loc90/th_96306_bd87_122_90lo.JPG[/IMG]</a>
    or:
    <a href="http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG">[img=http://img178.imagevenue.com/loc90/th_96306_bd87_122_90lo.JPG]</a>
    Anyone has an idea why is this? I have allready tried the report and TRX to process the idocs with status 30 and it didnt work.
    Thanks.
    Regards.
    Mariano Billinghurst

    Sorry i have posted wrong the images, here it goes again...
    Hi,  i have an interface IDOC to XI to JDBC, it has implemented a dedicated Queue, it dosnt have configured the acknowledge.
    it was working fine, then we implemented the dedicated queue, it works fine a cuple of thays but then the idocs start to have all status 30. (note: i have configured output mode 2)
    SM59 config image:
    http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG
    WE20 config image:
    http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG
    Table IDXQUEUE in XI SE16 image:
    http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG
    Function module in SE80 image:
    http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG
    First message that came out by de dedicated queue image:
    http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG
    Last message that came out by de dedicated queue image:
    http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG
    BD87 from the day that everything work fine to today image:
    http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG
    Anyone has an idea why is this? I have allready tried the report and TRX to process the idocs with status 30 and it didnt work.
    Thanks.
    Regards.
    Mariano Billinghurst

  • Assigning a dedicated queue for a Interface

    Hi Experts,
                     I have a proxy to Database scenario. I am sending data in chunks via proxy. I want the chunks to be inserted in to the database in the same order becuse in last chunk i am calling some additional Stored proc which will unlock the database after insertion so i want to do the following.
    1) I want to dedicate a separate queue which will contain all the messages from the Outbound Proxy (sending data to Database.)
    2) That queue should not contain messages from any other sender interface so that i can simply delete the queue and trigger the proxy again.
    Please suggest
    Thanks
    Vijay

    Hi,
    Check this prioritize messages in XI Using Queues
    How to prioritize messages in XI
    Regards
    Seshagiri

  • Dedicated Queue for Async Interface.

    Hi,
    I have a requirement , where a  message from interface should always go through same Queue .
    How to Achive this .
    Please suggets ...
    Regards
    PS

    Hi,
    Please refer below blogs,
    How to prioritize messages in XI
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc1869733413?QuickLink=index&overridelayout=true
    regards,
    ganesh.

  • SMQ2 Queue Monitering and stuck up problem

    Hello Experts ,
    Below is the situation
    u2022     An interface is asynchronous In bound in ECC from PI as a PROXY message and the quality of message is EOIO (Exactly once in order) i.e. it has a definite queue.
    u2022     The actual method of the Provider class has the code which posts the data into the ECC system using BAPI.
    u2022     If BAPI is successful the message is successfully passed BUT if BAPI returns an Error an exception is raised (CX_AI_APPLICATION_FAULT) and the errors are logged into Zee tables. After the resolution of errors the xml id is reprocessed using SXI_MONITOR  Tcode
    Concerns
    u2022     As the Message quality type is EOIO  it has a dedicated queue and if the first message in the queue fails  the queue is  in status  SYSFAIL  , as per in tcode SMQ2
    u2022     The status text for the ID in the Queue is - An exception occurred that was not caught.
    u2022     Due to this all the rest of the messages in the queue get stuck up i.e. Scheduled state, unless and until you go to SMQ2 and delete the message with the exception.
    u2022     Expected is that the queue should not stop or not go into SYSFAILT if an application exception is thrown.
    u2022     In our situation the message volume in the queue is LARGE may be 5K message a day.

    Anup Deshmukh wrote:
    Hello Experts ,
    > Below is the situation
    > u2022     An interface is asynchronous In bound in ECC from PI as a PROXY message and the quality of message is EOIO (Exactly once in order) i.e. it has a definite queue.
    > u2022     The actual method of the Provider class has the code which posts the data into the ECC system using BAPI.
    > u2022     If BAPI is successful the message is successfully passed BUT if BAPI returns an Error an exception is raised (CX_AI_APPLICATION_FAULT) and the errors are logged into Zee tables. After the resolution of errors the xml id is reprocessed using SXI_MONITOR  Tcode
    > Concerns
    > u2022     As the Message quality type is EOIO  it has a dedicated queue and if the first message in the queue fails  the queue is  in status  SYSFAIL  , as per in tcode SMQ2
    > u2022     The status text for the ID in the Queue is - An exception occurred that was not caught.
    > u2022     Due to this all the rest of the messages in the queue get stuck up i.e. Scheduled state, unless and until you go to SMQ2 and delete the message with the exception.
    > u2022     Expected is that the queue should not stop or not go into SYSFAILT if an application exception is thrown.
    > u2022     In our situation the message volume in the queue is LARGE may be 5K message a day.
    Why dont you have Fault message mapping , that captures the exception and trigger an alert using the alert framework..
    Best Regards,
    XA

  • Urgent..AQ Queue tables!!!

    Hi All,
    We have a scenario where we need to use AQ queues other than the predefined queues.
    So, I have the following doubts..
    Can i create more than one queue using the IP_QTAB as the Queue Table?
    Or is it a good idea to have a dedicated Queue Table created for a Queue?
    Any help is highly appreciated.
    Thanks,
    Deepti

    Hi Deepti,
    You might be interested in these threads -
    How to create a CUSTOM AQ internal delivery channel.
    Creating connection for AQ using JMS protocol
    Regards,
    Anuj

  • Message Queuing in XI

    Hello
    We are having multiple interfaces going through XI connecting multiple legacy systems to R/3. Message exchange occurs from multiple systems to and fro to R/3.
    Can it be possible to have a dedicated queues to individual legacy systems e.g. AS/400 system will get and post message on XI1 queue,Unix app will get and post msg on XI2 queue and so on?
    does anyone knows how to set that and also how to set the priority on messages?
    Thanks in advance.
    Regards
    Rajeev

    Hi,
    Did you check these links:
    http://help.sap.com/saphelp_nw04/helpdata/en/04/827440c36ed562e10000000a155106/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/b0/4c9240ed38ce62e10000000a155106/content.htm
    Regards,
    Sridhar

  • Content Based Queue Routing

    Is it possible to have a message routed to a particular queue based on some identifier within the content of the message?
    I have a situation where a certain message needs to take priority over other messages and the only distinguishing characteristic for this message will be embedded in the actual message. So, I would like to have a dedicated queue or pool of queues for this high priority message, ensuring quick processing.
    Any help is appreciated.

    Hi,
    There is no content based Queue routing in Receiver side. However, you can achieve, prioritized message processing by ensuring, high priority messages are processed first by registering queues with priority messages.
    For more on this:http://help.sap.com/saphelp_nw70/helpdata/en/04/827440c36ed562e10000000a155106/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
    Hope you are looking for this one.
    Rgds

  • Correlation for JMS Queue

    Hi,
    I have following scenario :
    Queue1
    Bpel1 -> Writes Schema A to Queue1
    Bpel2 -> Writes Schema B to Queue1
    Bpel3 -> Reads from Queue1
    I need that Bpel3 should read only Schema A from Queue and not Schema B.
    So how will i define the correlation between Bpel1 & Bpel 3.
    I tried fetching the processId in Bpel 1 and add it to Invoke property jca.jms.JmsCorrelation_id, but was not able to set the same in Bpel3.
    Any help/spec in setting up correlation for JMS Queues is highly apreciated.
    Thanks !!

    In standard JMS, an application can specify a correlation-id on per message basis using the javax.jms.Message API, and then specify a filter (a "selector") when creating a consumer via the javax.jms.Session API, but, in general, it is usually better to use a separate dedicated queue per business process (simplifies management, simplifies coding, improves perf, etc), or, if that's not an attractive option, to use a single MDB to dispatch messages from the same queue to different business processes. I don't know the specific steps to do the same in BPEL.
    You might want to try posting to the BPEL forum at BPEL
    Hope this helps,
    Tom

  • Locking Queue

    Hi All
    I have created a queue in SAP PI for serializing of IDocs. Now for testing I need to lock this queue, I went to SMQR and unregistered the queue which is resulting in flowing of IDocs using different queues.
    Can anyone tell me how can I lock that particular queue.
    Regards
    Sourabh

    Hi Sourabh,
    Check this blog: /people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
    Check SAP Note: 752194
    Normally, when a dedicated queue is assigned then it should be block the message when we de-register the queue.
    If you are not able to view the messages in queue, then unlock the queue from smq1/smq2.
    Thanks,

  • Architecture Question - End-User scalability of queues

    Hi,
    I have a question around the design / usage of Queues.
    We have a need for many client instances (sitting across business borders) to send data to a server instance and we're looking at Azure Service Bus / Message Queues to wire the clients-server together. One analogy of this architecture would be of an order
    system where many clients are sending their orders in, and the server responds with order status updates.
    Using a single queue to send/receive the data for the server appears straight forward, however my scalability query resolves around how the server queues notification messages back to a specific client in a secure manner. Would we need to create a queue
    per client to guarantee messages for one client are not picked up by another, or is there another "single-queue" scalable mechanism we could rely on (similar to a conversation)?
    Thanks,
    Jay :)
    If you shake a kettle, does it boil faster?

    Instead of creating a dedicated queue for each client you can create a single topic for order status updates. Here each client would receive from their own subscription with SAS authentication so that no client can read from someone else's messages.
    Here  is a good sample on using SAS over topics/subscriptions:
    https://code.msdn.microsoft.com/windowsazure/Using-Shared-Access-e605b37c

  • Messages getting scheduled in SAP ECC Box:Messages getting stuck in Inbound

    The scenario is -
    JDBC Sender-->> SAP PI-->> ECC Server(via ABAP proxy)
    The Interface is running properly in SAP PI & then the messages are getting posted to the Inbound queues in SAP ECC Box. Generally it takes few seconds for the messages to get processed, but now all are getting scheduled in the Inbound queues(in different channels as seen in SMQ2)
    We re-ran the interfaces again a few times, but all of them kept getting scheduled. Finally, after 2 hours one of the messages got processed. I suppose we won't face any problem now onwards.
    Though I can see several suggestions like registering the queues & assigning dedicated queues to the interface, none of the blog suggest the probable cause of the event?
    Can this be due to some issue in the server(heavy pressure of data in the server during the period/issue in the queues??)
    I found the following links regarding issues like these --
    XML file getting stucked in queue in ECC
    Message in scheduled state
    Thanks

    Is the printing issue with one specific printer or across system.
    What method you have configured for output device.
    There should be any issue if you add spool work process to Application server.
    Then you should be able to configure spool server load balancing. (Search on help.sap.com for spool load balancing)

  • Need to post Full Load data (55,000 records) to the target system.

    Hi All,
    We are getting the data from SAP HR system and we need to post this data to the partner system. So we configured Proxy(SAP) to File(Partner) scenario. We need to append the data of each message to the target file. Scince this is a very critical interface, we have used the dedicated queues. The scenario is working fine in D. When the interface transported to Q, they tested this interface with full load i.e with 55,000 messages.All messages are processed successfully in Integration Engine and to process in Adapter engine, it took nearly 37 hrs. We need to post all 55,000 records with in 2 hrs.
    The design of this interface is simple. We have used direct mapping and the size of each message is 1 KB. But need to append all messages to one file at the target side.We are using Advantco sFTP as receiver adapter and proxy as a sender.
    Could you please suggest a solution to process all 55,000 messages with in 2hrs.
    Thanks,
    Soumya.

    Hi Soumya,
    I understand your scenario as, HR data has be send to third party system once in a day. I guess, they are synchronizing employee (55,000) data in third party system with SAP HR data, daily.
    I would design this scenario as follows:-
    I will ask ABAPer to write a ABAP program, which run at 12:00, pickup 55,000 records from SAP HR tables and place them in one file. That file will be placed in SAP HR file system (you can see it using al11). At 12:30, PI File channel will pick up the file and transfer the file to third party target system as it is, without any transformation. File to File, pass through scenario (no ESR objects). Now, ask the target system to take the file, run their program (they should have some SQL routines). That SQL program will insert these records into target system tables.
    If 55,000 records make huge file at SAP HR system, ask ABAPer to split it into parts. PI will pick them in sequence based on file name.
    In this approach, I would ask both SAP HR (sender) and third party (target) system people to be flexible. Otherwise, I would say, it is not technically possible with current PI resources. In my opinion, PI system is middleware, not system in which huge computations can be done. If messages are coming from different systems, then collection in middleware makes sense. In your case, collecting large number of messages from single system, at high frequency is not advisable. 
    If third party target system people are not flexible, then go for File to JDBC scenario. Ask SAP HR ABAPer to split input file into more number of files (10-15, you PI system should be able to handle). At receiver JDBC, use native SQL. You need java mapping to construct, SQL statements in PI. Donu2019t convert flat file to JDBC XML structure, in your case PI cannot handle huge XML payload.
    You have to note, hardware upgrade is very difficult (you need lot of approvals depending your client process) and very costly. In my experience hardware upgrade will take 2-3 months.
    Regards,
    Raghu_Vamsee

  • JMS Receiver channel EOIO

    Hi,
    In SAP help, for one of the parameters of JMS Receiver channel it is mentioned that:
    Delivery Mode of Message Producer :
    Specify the quality of service of the message producer. You have the following options:
    u2022        Persist JMS Messages in the JMS Provider
    u2022        Do Not Persist JMS Messages in the JMS Provider
    Does this means EOIO/EO. I have proxy to JMS scenarios & like to send the data to JMS in EOIO.
    We are using Transport Protocol " Access JMS Provider with JNDI"
    With this I want to achieve, EOIO for Proxy to JMS. Pls let me know if Delivery Mode of Message Producer parameter would help & what should be the value.
    Thanks.

    Exactly Once messages are handled by default using status information in the J2EE server. All adapter error statuses and program terminations initialized externally are also handled in this mode. i.e.
    = persist jms messages in the jms adapter.
    Now if you specifically want to have dedicated queue; check manage queues under SXMB_ADM.
    See if you can set dedicated queue to your interface so that the messages can be processed in the sequence they have received.
    Also, once it is out of PI into target system (queue) the order will be maintained.
    Cheers!

  • Disable DSN for specific messages

    Hi,
    i have a problem, where i wish to disable DSN for specific internal users.
    Scenario :
    Interal User a sends a mail to special address c,
    if mail host of special address c is not available or anything else i wish that internal user a is never informed that c didnt recieve his mail.
    Can this be done ?
    i thought about doing this with sieve.. but i dont know if DSNs generated by the IMS Master itself are also checked by sieve mechanism....

    Please do notice that your bits do not support many of the features you want. And that later bits do. If you offer that to your company, perhaps you could update more often, or at least this time. We're not talking about a new package, here, but just an update to the one you have, that's not doing the job properly.
    Also, if you had asked for what you needed at the beginning, I could have helped you better.
    What you want is the sieve command, save-copy, or, perhaps monitor. Please see whitepaper, quoted below:
    Saving Messages for Document Retention
    If the reason you want to capture a copy of the message is for document retention, then you will want to take advantage of the new "capture" sieve action. You have to have iMS v5.2 or better to use this facility. The capture action can only be specified in a system or channel sieve; it is not available in user sieves. The general syntax is
    capture "monitoraddress"
    The monitor action is the same as the capture action. Users are encouraged to use the 'capture' instead of monitor as it best reflects the function being performed.
    This action sends a DSN containing the original message in its entirety to the specified capture address. Since this is a DSN it is effectively a completely separate message so there's little chance of it causing side effects that will alert anyone to the monitoring. In particular, no addresses from the original message appear in the DSN header so there's very little chance of the capture copy getting forwarded to the wrong person by mistake. And even though the original message is encapsulated, it is a MIME encapsulation which means the content is easily accessible in any MIME-compliant user agent.
    The capture action is nonstandard and undocumented. It was originally intended to be part of the habanero release, but the backporting of direct LDAP support to 5.2 means it is available in 5.2 as well. We certainly intend to support it in the future.
    Saving Messages for Replay
    There is an undocumented functionality in iMS for making a copy of messages for archival purposes. It's intended for saving sent messages in the event that they need to be replayed. We did this for folks who send mail via bad links to places where the mail may be received OK by an intermediate host but then subsequently lost on its way to the final destination.
    This is done with the MESSAGE-SAVE-COPY mapping table. Entries in that table have the form
    MESSAGE-SAVE-COPY
    out-channel|from-address|D|msg-filename result
    where
    out-channel -- name of the channel the message is flowing out
    from-address -- originator's address (envelope From: address)
    D -- the letter "D" (stands for "dequeue" )
    msg-filename -- name of the message file being dequeued.
    result -- where to rename the file
    Outbound Traffic
    To save only messages out to the Internet, do
    MESSAGE-SAVE-COPY
    tcp_local|*|D|/instance-root/queue/tcp_local/*/* (tab-or-space)$Y/msg_save/$1/$2
    Be aware that the archive isn't made until the message is actually dequeued from iMS (i.e., sent successfully or bounced). A rename operation is done (as opposed to a copy operation). As such, the message file has to remain on the same disk that the IMTA_QUEUE lives on.
    Inbound Traffic
    To capture inbound mail will want to have good control of what machines/pathways a message will take on its way into your systems. If your setup is such that mail always enters the site via an INBOUND relay and leaves the site via know outbound gateways, then inbound message flow is from INBOUND-MTA --> MsgStore machine.
    Since you can have multiple MsgStore machines behind any one INBOUND-MTA, you will want to make configuration on the INBOUND-MTA machine such that it will use a dedicated queue to talk to the MsgStore machines. For instance, on the INBOUND-MTA machine, you could setup a rewrite rule in your imta.cnf file for MsgStore-A, MsgStore-B, ... MsgStore-Z like:
    Node-A.store.domain.com.au $U%$D@tcp_to_store-daemon
    Node-Z.store.domain.com.au $U%$D@tcp_to_store-daemon
    and a corresponding 'tcp_to_store' channel which looks like:
    ! tcp_to_store
    tcp_to_store smtp mx single_sys subdirs 20 noreverse maxjobs 7 \
    pool SMTP_POOL maytlsserver allowswitchchannel \
    saslswitchchannel tcp_auth
    tcp_to_store-daemon
    This has the effect of routing all mail to any of your MsgStore machines through tcp_to_store channel. Transactions to other machines in your setup will take the tcp_intranet channel.
    With this in place you can then throw in a MSG-SAVE-COPY mapping table which reads:
    MESSAGE-SAVE-COPY
    *|*|D|/instance-root/imta/queue/tcp_to_store/*/* $Y/msg_save/tcp_to_store/$2/$3
    the net effect will be a number of queue files in the /msg_save/tcp_to_store directory which are ready for replay. Note the $2 in the sample represents the subdir that the message was already in. As such if you have 'subdirs 20' on your tcp_to_store channel, you will want to precreate the /msg_save/tcp_to_save/000 thru 019 subdirectories with the appropriate ownership and permissions.
    To initiate the replay, you want to simply move the /msg_save/tcp_to_store/### directories to the /instance-root/imta/queue/reprocess and issue the command 'imsimta cache -synch'. The MTA will start pushing out those messages to the store(s).
    If you want to have multiple replays happening you can kick off parallel runs of the reprocess channel by doing 'imsimta run reprocess &' a number of times.
    And, If you want to segregate the storage for each MsgStore machine, you can make new channel in addition to the one suggested 'tcp_to_store' channel. You would then have groups of rewrite rules directing traffic over those channels or you could have one rewrite rule per channel block that you setup. That way you can have distinct entries in your MSG-SAVE-COPY mapping table.
    Finally, since there is a rename operation taking place when you use the MSG-SAVE-COPY mapping table, you will want to make sure that at the first pass that /msg_save is on the same device that your queues live on.
    Short Term Arvchival
    You could setup a process in cron to move those files to a new device on a periodic basis. Better yet, schedule this via the job_controller. For instance, these lines at the top of your job_controller.cnf file:
    [PERIODIC_JOB=archive_mover]
    command=/usr/iplanet/sitescripts/arc_mover.sh
    time=/00:10
    will run the arc_mover.sh script for you every 10 minutes. Your arc_mover.sh could look something like:
    #!/bin/ksh
    # ***Script is untested - should generate some ideas though****
    DUMMY=`test -d /var/tmp/timestamp.dir || mkdir -p /var/tmp/timestamp.dir`
    cd /msg_save
    # First pass
    for dir in `find ./ -type d`
    do
    DUMMY=`test -d /real/storage/area/$dir || mkdir -p /real/storage/area/$dir`
    cd $dir
    for msgfile in `find ./ -type f -newer /var/tmp/timestamp.dir -name "*.00"`
    do
    mv $msgfile /real/storage/area/$dir/
    done
    cd /msg_save
    done
    touch /var/tmp/timestamp.dir
    # Second pass cause we do not know how long we took.
    for dir in `find ./ -type d`
    do
    DUMMY=`test -d /real/storage/area/$dir || mkdir -p /real/storage/area/$dir`
    cd $dir
    for msgfile in `find ./ -type f -newer /var/tmp/timestamp.dir -name "00"`
    do
    mv $msgfile /real/storage/area/$dir/
    done
    cd /msg_save
    done
    exit

Maybe you are looking for