Run Sender Communication channel for every 4Hrs

Dear all,
I have requirement to schedule sender CC in production for every 4hrs.
We have option called daily but not hourly !!!
Is it possible  to schedule sender CC like this for every 4hrs??
Note: For Some reasons i can't increase the polling to 4hrs in sender channel to solve this issue
Regards

Bhavana,
Found a solution. Create a unix script and run the command to start and stop the communication channel as per your requirement.
Below is the syntax.  You can try using wget command or curl in unix followed by the below command
http(s)://host:port/AdapterFramework/ChannelAdminServlet?party=party&service=service&channel=channel&action=action
wget http(s)://...
or
curl http(s)://...
check this link
/people/william.li/blog/2007/05/04/control-communication-channels-externally-without-using-rwb

Similar Messages

  • Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

    Hello All,
    One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
    Is the (IDoc) Communication Channel from Sending system to XI required to configured?
    Many thanks in advanced!
    Jochen

    Hi Jochen,
    for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
    Thanks,
    Rajeev Gupta

  • Can we schedule sender file channel for every 2 hrs??

    Hi all,
    I want to run sender channel for every 2hrs. i searched in Availability Timings but there is no such facility to schedule the channel for every 2 hrs
    There is an option to schedule the channel on daily basis and for how much duration time it should run.
    This won't work in my case
    please share your thoughts...
    Regards

    Hi RP,
    >>in the configuration of CC sender file --> poll interval(secs) = 7200. this value is equals to 2hs
    problem solved right?
    Good Idea, but the problem here is a i explained above this is combination of 2 interfaces
    1) Idocs will be triggered every 2 hrs in ECC and records will be appended to single file on XI Shared drive.This is one interface
    2) Another Interface is to pick up the appended big file From XI Shared drive to FTP Server.
    EX:
    If all Idocs triggered at 1:30pm from ECC----all records will be appended to single file suppose by 1:31pm
    Now in second interface i gave poll interval as 7200 and activated at 1:40pm, so the file will be picked up at 1:40pm
    So this frame of time interval continues smoothly like next job is ecc will run at 3:30pm and appends to file by 3:31pm there by second interface will pick up at 3:40pm. This is the correct way of execution
    PROBLEM: In this process, If my PI server is down at 2:00pm and is up at 4:11pm, there won't be any problem with first interface.my second interface starts from 4:11pm(server up time) onwards and keep polling for every 2 hrs from there onwards. so my total time frame is collapsed .
    Regards

  • BIC Module Error in Sender Communication channel for EDI to File scenario.

    Hi Experts,
    We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
    Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
    Thanks & Regards,
    Abhishek

    Hi Abhishek,
    Is there any special character present in the EDI file?
    the parser is not able to parse the data.
    you can check the BIC conversion log for more information.
    Regards,
    Harish

  • Sender communication channel for  HTTP and IDOC

    Why the sender communication channel is not necessary for HTTP and IDOC

    Hi,
    Because they lie on ABAP stack ie on Integration Engine...so that they can process directly but other adapter lies on Adapter engine.
    Regards
    Hemant

  • Regd Sender  Communication channel

    Hi all,
    I have configured a sender communication channel for picking a file. Everything looks fine to me, but the file is not getting picked up.
    I checked in RWB for channel, channel is configured fine.its says  processing started, and processing finished successfully.No message ID is showing.But the file is not getting picked from the location.
    In moni , no messages to display.
    can you suggest how to trace out the possible error? the path and file names are perfect, check it number of times.

    Hi Anika,
    in sender file comm channel, set the processing mode to delete and activate it.............
    then in source file system, ask the file system guys to check the file permissions of the source file........it should have read, write, execute for others............
    then your source file should be picked.........if still your source file is not getting picked, then ask your basis guys to do a full CPACache refresh using PIDIRUSER and then re-run your scenario......
    Regards,
    Rajeev Gupta

  • 5 Sender communication channels and 1 receiver channel

    My scenario demands to handle 5 different select queries from single data base.
    I need to have 5 sender communication channels for editing an employee and only 1 receiver channel at receiver side and i'm using one common Functional module to handle.
    Can i handle the above situation in one single interface??? like having 5 sender communication channel at sender side and 1 receiver communication channel at receiver side??
    Thanks
    LN

    like having 5 sender communication channel at sender side and 1 receiver communication channel at receiver side??
    Yes it is possible....if it is not possible for you to combine the query into one.
    How is the data to be processed? Is the data pulled by the 5 sender channels, to be merged into one target message? Is yes then you have to make use of a BPM.
    If the Data from 5 sender channels will be individually forwarded  to the receiver channel then there is no need of a BPM.

  • HOW TO CREATE SERVICE FOR SENDER SOAP COMMUNICATION CHANNEL FOR ECC PROXY

    Hi Experts,
    I need generate the service for sender soap communication channel for target url to receive the  inbound proxy.
    my scenario is like SOAP to proxy. while using  receiver proxy also we are planing using AAE method .
    i am using SOAP sender and SOAp receiver communication channel .i need to provide the target url for this communication channel.
    how to generate the url for this and what is the transaction code .
    Please help us.
    Regards
    Ravinder.S

    Hi Ravinder,
    Q.my scenario is like SOAP to proxy. while using  receiver proxy also we are planing using AAE method.
    SOAP to Poxy in this case.
    For sender  SOAP system, we can generate the WSDL link in ID part.
    for Reveiver proxy give the integration engine URL.
    http://IP:PORT/sap/xi/engine?type=entry
    how to generate the url for this and what is the transaction code
    There is no transaction code for generating the URL.
    i hope this will help.
    Regards,
    Kesava.

  • Why is a sender communication channel not required for IDOC and PROXY ?

    Hello,
    In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
    Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..)  when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
    Though this might be a regular question, I am not able to find a proper reason.
    Please let me know the reason for the above request.
    Thanks & Regards.

    You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
    But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
    Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
    Regards,
    Raj

  • JMS Sender Communication  Channel problem

    Hi XI gurus!!
    I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
    In defaultTrace.XX.trc I see the following information and errors:
    #1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
    #1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#[email protected]#
    {GenericConnectionProfileImpl
    {Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
    JmsMessageSelector=,
    ConnectionFactoryConstructor=null,
    ConnectionFactoryFactoryInvocation=null,
    ConnectionFactoryInvocations=[],
    DestinationConstructor=
    {ConstructorInvocation
    {className=null,
    invokeParams=[]
    DestinationInvocations=[],
    MessageInvocations=[],
    DestinationName=null,
    User=,
    Password=,
    isJmsSessionTransacted=true,
    InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
    LookupConnectionFactory=QueueConnectionFactory,
    LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
    SerializedConnectionFactoryPath=null,
    SerializedDestinationPath=null,
    Flags=0000000000000000000000000000000000000000000000000000100000000010
    #1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
    #1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
    #1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
    #1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    #1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
    In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
    Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
    BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
    Thanks

    HI,
    As per the trace details given please consider few of the below options....
    What do u see in adapter monitoring tool for JMS adapter?
    http://hostname:5XX00/mdt/amtServlet
    Did you follow the document on correlation of JMS messages?
    In communication channel You have to set
    Correlation ID -> XI conversationID
    XI message ID->GUID
    XI Conversation ID -> JMS correlation ID.
    Now in the custom J2EE application you should set
    jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
    This thread deals with the issue..
    JMS Queue monitoring
    Check  if the JMS Sender adapter EOIO is with serialized messages 
    Thanks
    Swarup

  • JMS (Sender Communication Channel) and MQ in Mainframe (Legacy) System

    Hi All,
    Can we use JMS Sender Communication Channel in XI that runs on Windows 2003 server to DIRECTLY poll messages from MQ in Mainframe (Legacy) system??
    I understand that we can install MQ on XI server and have mainframe push the messages to XI MQ so that JMS can poll but wanted to see if there is a way to do this without having MQ on XI server.
    If you know of any documentation regarding this, can you please post it?
    Thanks,
    Jay

    Jung,
    Are you looking for this help:
    /people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
    Also check this sap help:
    http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
    ---Satish

  • JDBC Sender Communication Channel Problem

    Hello everybody,
    I have a sender communication channel, it is with green Functioning status in channel monitor in runtime workbench, and the log says "Process started" for every pool as configured, but it doesn't return any data to XI, and there's data to be taken, the problem started a few hours cause it was working fine, I've already executed a Complete refresh cache in SXI_CACHE, and changed the channel from Active to Inactive in ID, and Stopped and Started it again in RW, it doesn't give any errors, but it doesn't bring back any data that should be, any suggestions or maybe any information on how to refresh totally those channels????, thanks in advance.
    Regard's
    Paul

    Hi Paul
    Check for JDBC adapter locks. cpa cache locks are not relevant to your problem.
    Moreover check with the visual admin logs as well. if you can get info about the issue you have
    Thanks
    Gaurav

  • FILE SENDER COMMUNICATION CHANNEL DOESN'T GET FILE

    Hi,
    I have create a new sender communication channel with ftp file configuration. Server parameter and source directory are correct.
    I have also checked file and directory permission (chmod 777)
    Poll interval is 600 secs.
    There is no error in communication channel monitor  (returned log: CC is correctly configured and started).
    Process started every poll interval, but no file is picked up.
    Why?
    Carme

    Hi,
    What type of file are you processing. Check whether the file type is binary or text mode.
    Also check whether the file name you have specified in the CC and the exact file in the directory are the same.
    Also check the file processing mode, whether it is read only, delete or in test mode.
    If the file is in read only mode when the file first processed, then once the file was processed it would be in read only mode, so if you place the new file it should process, so try deleting the existing file in the directory and place a new file with exact file name along with the correct extension and try to process it.
    Also I would suggest you check the exact file extension, by unchecking the radio button in the folder option under the menu tools> Folder options> view-->hide extension for file type.
    Regards,
    Nithiyanandam

  • XI-Multiple instance scenario -File & SQL sender communication channels

    Hi
       i have a basic question regarding how file sender communication channel ( where we poll for a particular file pattern either using file/ftp types in a particular subfolder ) or a sql sender communication channel - ( selecting records from a sql source ) would work in a scenario with two active XI instances and j2EE file and sql adapter services running on both of the J2EE servers ?
    1. How would the file polling from both J2EE servers - avoid a conflict looking for the same file pattern ? Is there any inbuilt mechanism from SAP to make multiple instances work with the file polling - without a confict ?
    2. Simlar question for SQL sender type communication channel ?
    If SAP does have a mechanism to handle multiple instance scenarios for file and sql sender adapter based communication channels, is there a link/document on this ?

    Hi Karthik,
    Please see my comments.
    I am just wondering aloud - what will happen if we use a select for update clause in the sql sender adapter communication channel -
    Gouri: Yes you can use select + update. In fact that is the right way.
    will this ensure that polling from one J2EE instance will lock the selected records so that the second instance does not select the same set of records from the sql server ? Or should we not use a select for update and use a simple select statement ?
    Gouri: Yes. SQL DB will ensure that same data will not be picked by another node. As I mentioned earlier use serilizable option from advanced mode.
    -Gouri

  • Configuring a Communication Channel for an AE other than the default IS

    Configuring a Communication Channel for an Adapter Engine other than the default engine.
    See:  help.sap.com for Communication Channel http://help.sap.com/saphelp_nw04/helpdata/en/1b/d5ef3b1ad56d4fe10000000a114084/frameset.htm
    It states under 'Adapter Configuration', that you can specify the Adapter Engine you want to use in the Adapter Engine dropdown box.
    I have activated the XI components on my ERP system using transaction SICF, but what do I have to do to make the other adapter engines show up in the dropdown list when configuring an adapter?
    Maybe some background would be helpful:  This is for a scenario that will send a file from an external system to one of the ERP systems in our landscape.  BUT, the system admins have decided to revoke our FTP accounts (because they have their reasons), so I need to create a File Adapter that will drop the file on the file system of that ERP system, due to visibility I want to use the integrated Adapter Engine that comes with the ERP system, but need to know how/what I'm missing in setting up this scenario.

    Hi Anesh,
    >>>>but what do I have to do to make the other adapter engines show up in the dropdown list when configuring an adapter?
    in order to use some other adapter engine you
    have to install it first by dafault only one
    (central) adapter engine is used and it is all
    most clients need
    if you'd like to use some other adapter engine
    (decentralized for example) have a look at thid guide:
    <b>Configuring a Local Adapter Engine to Work with a Central Instance</b>
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Maybe you are looking for