Idoc Sender Configurations

Hi,
Our requirement is to do Idoc to File scenario in which what are all the configurations that are to be done in R/3 and as well as in XI server.
regards,
Kishore

Hi Kishore,
Please go through /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
also i give a quick checklist, chk it out.
1)Create an RFC destination to XI in the sender SAP system using SM59
2)Create a transactional port to XI using the RFC destination created in the above step
3)Create a Partner agreement usign transaction we20 and port using we21 in the sender SAP system
4)Create a logical system using transaction bd54 for the partner agreement created in the above step
5)Select an IDOC using transaction we19 and change the EDIDC header recepient port & LS name
6)Create an RFC destination to the Sender SAP system using SM59
7)Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
8)Create SLD entries(technical and business system) for the sender SAP system.
In IR , import IDOC metadata, create ur target XSD , create ur Message Mapping , Interface Mapping, thats it.
In ID, import ur sender R/3 system & receiver systems, U dont need a IDOC sender CC , so only File receiver CC is reqd. Now create a receiver determination, interface determination & receiver agreement ,activate & ur done.
Use WE19 , select an IDOC and do an outbound processing and u shud see the IDOC in XI.
Rgds
joel
Edited by: joel trinidade on Feb 23, 2009 2:44 PM

Similar Messages

  • Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

    Dear Experts,
    My configuration scenario is  outbound:   SAP (IDOC)-------->PI------->AS2 ThirdParty.
    SAP PI version: 7.31 dual stack.
    First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
    http://scn.sap.com/docs/DOC-34155
    http://scn.sap.com/docs/DOC-31398
    While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
    Could you please help me on this issue ,I will appriciate you .This is very urgent.
    Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
    and I are getting below error in SM58 ECC system.
    Error in  ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
    Thanks,
    Aadi

    Hi Aadi,
    Please check the below SAP notes
    1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
    1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
    reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
    also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
    regards,
    Harish

  • Sender configuration incomplete - perhaps AS2ID missing...

    Hello,
    We have an PI 7.11 system. Our scenario is outbound IDOC to AS2 (converted to EDIFACT). It is from R/3 --> PI --> Third Party. We installed SeeBurger adapters.
    R/3 is in our landscape, its component created without Party.
    Receiver is a Third Party. So its component created with Party. In party we have defined  Agency and Scheme Name as "Seeburger", "AS2ID", "XXX".
    We also have done Receiver Agreement Header Mapping only for Receiver Communication Party and Receiver Communication Component.
    When we try to send a message, getting below error at audit log.
    Our Sender system is R/3, therefore we cant define a Party for it. What should be resolve this issue?
    2012-03-08 15:37:49 Information Message successfully put into the queue.
    2012-03-08 15:37:49 Information The message was successfully retrieved from the receive queue.
    2012-03-08 15:37:49 Information The message status was set to DLNG.
    2012-03-08 15:37:49 Information Delivering to channel: Receiver_Channel_AS2
    2012-03-08 15:37:49 Information Message entered AF MP exit bean and will be passed to the JCA adapter now.
    2012-03-08 15:37:49 Information SEEBURGER/AS2: Received order from system.
    2012-03-08 15:37:49 Information Acknowledgement creation triggered for type: AckNotSupported
    2012-03-08 15:37:49 Error Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing..
    2012-03-08 15:37:49 Error Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing..
    2012-03-08 15:37:49 Error Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DATABASE. Sender configuration incomplete - perhaps AS2ID missing...
    2012-03-08 15:37:49 Information The message status was set to WAIT.

    Hello,
    Did you solve the problem? What was the solution?
    I have the same issue.
    I have one AS2 scenario with this error and 20 other scenarios working fine.
    full cache refresh is done, but did not solve the problem.

  • Error to IDOC Sender

    Dear Experts,
    I have a requirement to send error information back to the IDOC Sender. The scenario is IDOC --> PI --> TargetSystem (ASYNCHRONOUS).
    If there is an error in processing within SAP PI, then the error should be propagated to the SAP system (IDOC), so that the Business can take note of the error.
    As far as I know, we can configure Alerts in SAP PI and in case of an error the recipient will get the alert message. But how to send the error message back to sender in case of an IDOC
    I do not want blogs on how to configure alerts in ALRTCATDEF
    Thanks.

    although I think you mean the person that triggered the IDoc, ie. someone who created a SalesOrder, which was then sent
    to PI.
    Yes, this is what is required.
    With this UserID you can do a lookup in the sender system, to retrieve the email-adress in the User Master Data record.
    Then use this email adress to send an alert,
    How exactly the lookup will be done? I have a message processing running in SAP PI, suddenly something goes wrong (lets say there is a mapping error) and the processing stops there. Now how to do a lookup (from where)? Configuring a fixed recipient in ALRTCATDEF wont work as we dont know who will trigger the IDOC!
    Any reference on how to perform lookup when message fails in XI/ PI will be helpful.
    Thanks.

  • Why IDoc Sender Channel Used in Outbound Scenario's

    Hi Team,
    In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
    Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
    Can you give me clear idea on it / suggect any blogs.
    Thanks.
    Drumi

    HI,
    In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
    Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
    we dont necessary to create Sender Communication channel for IDOC and Proxy and http because xi and sender systems(out bound) resides on abap stack and also dont need for any idoc.
    The reason is that R/3 can directly send Idocs to XI via ALE layer using RFC destination specified in SM59.
    This IDoc after reaching XI is converted in IDoc-XML. This is done when we specify IDoc metadata IDX2 in XI. It is then used in IR for mapping.
    Now for the receiver side, when IDoc-XML is created after mapping program run is sent to R/3. Before that, it has to
    be converted into IDoc. This conversion is IDoc-XML to IDoc is done by IDoc Receiver adapter.
    one case we need to create sender IDoc Communication channel for IDOC packaging concept thats all.
    thanks,
    Edited by: bhavanisankar.solasu on Dec 16, 2011 7:12 AM

  • IDOC sender: Error in Logical system name?

    Hi,
    In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
    Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
    Following is already checked:
    1. SLD has maintained the proper logical system name for the P2P system
    2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
    3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
    On the receiver system, the followed error is shown as follows:
    - <STANDARD>
      <CONTROLLER />
      <FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
      <FAULT_URL />
      <FAULT_DETAIL />
      </STANDARD>
    Thanks in advance for the useful answers.
    Sowkhya

    Hi,
    1. R/3 system's logical system name and SLD business system's logical system name has the same.
    Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
    2. SLDCHECK shows following message:
    Summary: Connection to SLD does not work
    The issue still persists. Will SLDCHECK correct solve the issue?
    Regards,
    Sowkhya

  • IDOC send step not running with exception in BPM?

    Hello,
    hope this is a simple question, but we are running with a problem here which is not answered well in SAP help or sdn. Possibly I didn´t find the right blog.
    Situation:
    We created a BPM with a send step (IDOC receiver) in a block (after a receive step starting the BPM) (That´s simple so far!).
    The send step (async IDOC) in the block is connected in its attributes in field "system error" to an exception branch defined in the same block.
    In this except.branch the process should send back to sender system a message via RFC and the last step in this exception branch is to interrupt the proces.
    But now we tried to do a test. In this test we modified the receiver address of the send step (IDOC reciver) so that the receiver could not be reached, which results in a system error in SXMB_MONI (Service unavailable).
    But this doesn´t work. The BPM starts the send step to the unavailable receiver, SXMB_MONI shows a system error step, but then the BPM continues with the next step after the block without starting the exception branch.
    Any idea why the exception branch is not called?
    Best regards
    Dirk

    Hello again,
    we are one step further now.
    We did the same with an RFC instead of the IDOC send step.
    Same result:
    The service is not reachable. So the step results in an system error.
    But as we could see in the monitoring SXMB_MONI the block with the exception and this send step (RFC) is passed before the step gives back this error!
    So it looks like connection problems do not trigger an exception?
    Any help is welcome!
    Best regards
    Dirk

  • IDOC sender system settings

    Hi,
    I am trying to do the settings for the idoc sender system the steps i have completed are..
    1) sm59..maintain a rfc destination from idoc sender to the integration server.
    2) we21..created a tRfc port with the rfc dest from step1.
    step 3 is where i am stuck...
    3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
    any pointers..would be appreciated.
    Regards
    Ravi

    ALE settings.
    <u><b>SAP XI</b></u><b>1) RFC Destination (SM59)</b>
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    <b>h) Test the connection and remote logon.
    2) Create Port (IDX1)</b>
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP XI towards other system.
    e) Save
    <b>3) Load Meta Data for IDOC (IDX2)</b>
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    <u><b>SAP R/3</b></u>
    <b>1) RFC Destination (SM59)</b>
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    <b>2) Create Port (We21)</b>
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    <b>3) Create Partner Profile (WE20)</b>
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    <u><b>In SLD – System Landscape Directory</b></u>
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    <b>In Transaction SALE</b>
    Define and Assign the logical system name.

  • Idoc sender issue

    Hi,
    I have an issue in Idoc sender scenario.
    The flow is Idoc to BPM to Flat file.
    Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.
    Which transaction to use to trace Idoc in XI?
    I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.
    Regards,
    Anirudh.

    Hi
    Go through following ALE step, check whether you missed any of these steps:
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    Regards
    Sami

  • R/3 to XI manually IDOC sending and problem:

    <u><b>R/3 to XI manually IDOC sending and problem:</b></u>
    I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    I check XI (sxmb_moni) but there is nomessage there.
    <b>Problem 1:</b> I don't want R/3 ask me UID and password for XI access
    <b>Problem 2:</b> I want to see message in XI (sxmb_moni)
    Thanks

    Hi Cemil,
    >>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    check the RFC destination from R3 to XI (SM59)
    you will find the right one from your port (We21)
    you can also check step by step procedures
    for IDOC - XI in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Message mapping: SOAP Receiver to IDOC Sender

    hi,
    i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
    IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
    The SOAP Response will not have the PO Number and the Vendor Name.
    How can i have the Reason of failure, PO Number and Vendor in one message type?
    Thanks in advance,
    Tirumal

    Praveen -
    Thanks for the response and appreciate your observation.
    Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
    There are lot of vendors who run their proprietary web services. So cannot change their stuff.
    How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
    I created a SOAP Response Type with the "Reason Code" information.
    I created another message type with all the information that i want.
    How would i map the SOAP Request to the SOAP Response msg type and the other message type.
    Let me know.
    Thanks in advance,
    Tirumal

  • Idoc adapter configuration

    while idoc adapter configuration we uncheck the option " apply control record values from payload" why and when it will be usefull?

    Hi Sudhakar,
    When you want to map control record values from the Target payload .....
    Then you choose the option apply control record from payload.
    Follow the link below to understand the concept better....
    (Configuring the Receiver IDoc Adapter --> Fields of the IDoc Control Record)
    http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/frameset.htm
    Regards,
    Sushil.

  • IDoc Adapter configuration for very high volumes

    Hi PI Expert,
    I'd like to have some tips about Idoc Adapter configuration in case of very very hudge volumes in "file to Idoc scenario" (adressing ECC) : How to optimize Idoc transmission time PI -> ECC ?
    => parallelization PI -> ECC by using differents comm channel IDocs with differents RFC destinations ?.
    => some other technical parameters in adapter IDoc
    => ...
    Thanks a lot
    Best regard.
    Etienne

    Hi,
    for sure idoc bundling will greatly increase performance: https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken]
    If you are in 7.1 you can also leverage message packaging: http://help.sap.com/saphelp_nwpi71/helpdata/en/46/79e8e13872275ae10000000a11466f/frameset.htm
    Regards,
    Sergio

  • Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured

    Today I tried to configure JAVA APM on a CentOS 6.4 server with tomcat6 installed through the normal RPM package. Adding this server to SCOM was no problem and it shows itself as a 'Deep Monitored Configuration'. The last part of enabling
    JAVA APM fails. I have followed the following process:
    1. Imported the JAVA APM MP's
    2. Extracted the JAVA APM Files
    3. Copied those files to my CentOS server
    4. Added the JAVA_OPTS to my tomcat configuration file
    5. Restarted Tomcat
    When I look for the log file which needs to be created through the installation of the APM agent it cannot be find. When I look into my Catalina.out file I see the following errors:
    Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
    SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
    com.microsoft.ManagementServices.APMAgent.Exception.ApmException: SEAgent.config.xml does not have a valid event sender configured
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            ... 15 more
    Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            ... 15 more
    Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            ... 19 more
    Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.InstantiationException: Monitor initialization failed: SEAgent.config.xml does not have a valid event sender configured
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            ... 12 more
    Does anyone have seen this error before? Can someone help me with this one?
    Thnx,

    I'm running tomcat on a CentOS release 6.4 (Final) server. I installed Tomcat 6 through an RPM from the CentOS sources. I have installed Apache Tomcat/6.0.24 wit JVM version 1.7.0_09-icedtea-mockbuild_2013_01_16_18_52-b00, the JVM Vendor is Oracle Corporation.
    My tomcat configuration needs to be done in '/etc/tomcat6/tomcat6.conf'
    I installed the APM Agent in the path '/opt/apm/' with the rights  40755 (root/root). The files have the following rights:
    -rw-rw-r-- 1 root tomcat  32046 Mar  3 15:38 apm_facade.jar
    -rw-rw-r-- 1 root tomcat 244819 Mar  3 15:38 apm_monitor.jar
    -rw-rw-r-- 1 root tomcat  38110 Mar  3 15:38 apm_producers.jar
    -rw-rw-r-- 1 root tomcat 207006 Mar  3 15:38 asm-all-3.3.1.jar
    -rw-rw-r-- 1 root tomcat   4157 Mar  3 15:38 ASM_Third_Party_Notices.txt
    -rw-rw-r-- 1 root tomcat 241368 Mar  3 15:38 DispatcherStub.dll
    -rw-rw-r-- 1 root tomcat  36880 Mar  3 15:38 pmonitor.config.xml
    -rw-rw-r-- 1 root tomcat   2625 Mar  3 15:38 SEAgent.config.xml
    -rw-rw-r-- 1 root tomcat    830 Mar  5 15:19 Starter.properties
    The above rights are equal to the /etc/tomcat6 directory with the tomcat configuration files.
    In the tomcat6.conf I have added the following entries:
    #Microsoft SCOM APM
    JAVA_OPTS="${JAVA_OPTS} -Djava.library.path=/opt/apm"
    JAVA_OPTS="${JAVA_OPTS} -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar"
    When I look into the running tomcat process I see the following:
    tomcat   17401     1  0 Mar05 ?        00:00:39 /usr/lib/jvm/jre/bin/java -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar
    -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory
    -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat6/temp
    -Djava.util.logging.config.file=/usr/share/tomcat6/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
    My Starter.Properties looks like this:
    # Jars to load by inner classloader.
    # Use semicolons to separate the JAR entries
    ClassPath=apm_monitor.jar;asm-all-3.3.1.jar;apm_producers.jar
    # Path to pmonitor.config
    MonitorConfigFileName=pmonitor.config.xml
    # Path to SEAgent.config
    AgentConfigFileName=SEAgent.config.xml
    # Log file name
    # Example for full-path location:
    #                  LogFileName=c:\\tracelog\\apm-java-agent.log
    # Example for relative path (to agent jar files):
    #                  LogFileName=apm-java-agent.log
    LogFileName=apm-java-agent.log
    # Log level (SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST)
    # A level of FINER or FINEST may expose Personally identifiable
    # information (PII) in the log file.  The levels below INFO are
    # intended for debugging and diagnostic use only.
    LogLevel=FINEST
    The 'apm-java-agent.log' is not created on the system. The only logging is done in the catalina.out. When restarting tomcat I see the following entries in te log file:
    INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading succeeded (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger warning
    WARNING: Failed registering the COUNTER MBean
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
    SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Hope this gives your some more background around my problem, I double checked the permissions..

  • AS2 Sender configuration - Authentication Certificate

    Hello guys,
    We're implementing EDI with a partner with AS2. We have AS2 sender adapter configured. Everything works fine (we're able to receive data from partner and send back MDN) without signing.
    Now we're working on getting data signed. We have uploaded partner cert to keystore (TrustedCAs) and have provided partner with our certificate as well.
    On Sender agreement--> Security Settings --> AS2 Sender Configuration --> Authentication Certificate how do we specify the certificate we're using. Should it be just the fullname like TrustedCAs/PartnerCert ?
    Also How should we specify the Decryption Key and Signing Key under AS2 Receiver Configuration?
    I was expecting to be able to choose from available keystores, but it is a free text field.
    Can anybody please help me on this?
    Thanks
    Karthik

    Hi Karthik,
    >>On Sender agreement--> Security Settings --> AS2 Sender Configuration --> Authentication Certificate how do we specify the certificate we're using. Should it be just the fullname like TrustedCAs/PartnerCert ?
    You need to mention the fullname  as TrstedCAs/PartnerCert.
    >>Also How should we specify the Decryption Key and Signing Key under AS2 Receiver Configuration?
    Yes you need to since you are using signed messages here..
    Regards
    Suraj

Maybe you are looking for

  • My junk, trash, etc. folders are no longer showing up as a menu!!

    When I open my mail window all it says at the top is Important and shows an icon called Messages. I cannot find the way to get back to my email address so that I can access the Trash folder, the Junk folder, the Sent folder, etc. I find this frustrat

  • Batch specific unit of measure - Purchase order history correction

    I have maintained an alternate proportional unit for a material.  This alternate unit is used as the order price unit in the purchase order.  I have created a batch characteristic which is linked to this proportional unit of measure. I have also crea

  • Airport only works on certain computers...

    I have two APX and two AX. Even if I use just one APX still only my 15in powerbook will have inernet. My other computers (G4 Cube, and two older iBooks) will recognize my network, but in the network status pane in system preferences it registers yell

  • Grant Privileges in Database Vault for DATAPUMP.

    HI, I am using ORACLE DATABASE 11g R2. I have installed/enabled DATABASE VAULT 11g on it. I have configured many user in it for privileges like 'SELECT on table','INSERT on table' ,DELETE ..... I want to give a user DATAPUMP privilege so that he can

  • MacBook Pro battery capacity dropped to 2%?!?!?!

    Hi Everyone I've recently noticed my battery capacity has dropped DRAMATICALLY in the past month. It's the 2.0GHz quad-core i7 15 inch MacBook Pro, early 2011 model. It is 15 months old, however I bought it brand new (box not even opened) from an eBa