Integrating the J2CA 1.5 Cics Queue Adapter for Inbound.

Hi all, I'm trying to create a MessageDrivenBean which consumes messages from cics, but when I try to deploy my mdb I receive this message .
message-driven bean 'AttuTestReceiverBean' that is not configured with JCA resource adapter must implements the onMessage method of the javax.jms.MessageListener interface
Here is my ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee">
<enterprise-beans>
<message-driven>
<description>Message Driven Bean</description>
<display-name>AttunityMDB</display-name>
<ejb-name>AttuTestReceiverBean</ejb-name>
<ejb-class>attutestreceivebean.AttuTestReceiverBean</ejb-class>
<messaging-type>javax.resource.cci.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>userName</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>password</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>firewallProtocol</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>connectTimeout</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>encryptionProtocol</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>encryptionKeyName</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>workspace</activation-config-property-name>
<activation-config-property-value>CICSINBOUNDEvent</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>portNumber</activation-config-property-name>
<activation-config-property-value>2552</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>useNamespace</activation-config-property-name>
<activation-config-property-value>true</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>networkXMLProtocol</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>idleTimeout</activation-config-property-name>
<activation-config-property-value></activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>messagesInBatch</activation-config-property-name>
<activation-config-property-value>50</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>support2PC</activation-config-property-name>
<activation-config-property-value>false</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>waitTime</activation-config-property-name>
<activation-config-property-value>30</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>retryInterval</activation-config-property-name>
<activation-config-property-value>15</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>eisName</activation-config-property-name>
<activation-config-property-value>CICSINBOUNDEvent</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>serverName</activation-config-property-name>
<activation-config-property-value>207.169.19.101</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>exposeEventStreamMetadata</activation-config-property-name>
<activation-config-property-value>true</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>AttuTestReceiverBean</ejb-name>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.resource.cci.Record</method-param>
</method-params>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
My orion-ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<orion-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-ejb-jar-10_0.xsd" schema-major-version="10" schema-minor-version="0">
<enterprise-beans>
<message-driven-deployment
name="AttuTestReceiverBean"
destination-location="AttunityMDB"
connection-factory-location="eis/legacy/AD_CICS_COBOL"/>
</enterprise-beans>
</orion-ejb-jar>
And my MDB class
package attutestreceivebean;
import com.attunity.adapter.core.CoreDOMWriter;
import com.attunity.adapter.core.CoreDomRecord;
import javax.ejb.EJBException;
import javax.ejb.MessageDrivenBean;
import javax.ejb.MessageDrivenContext;
import javax.jms.Message;
import javax.resource.cci.MessageListener;
import javax.resource.cci.Record;
import org.w3c.dom.Element;
public class AttuTestReceiverBean implements MessageDrivenBean,
javax.resource.cci.MessageListener{
private MessageDrivenContext _context;
public void ejbCreate() {
public void setMessageDrivenContext(MessageDrivenContext context) throws EJBException {
_context = context;
public void ejbRemove() throws EJBException {
public Record onMessage(Record record) {
CoreDOMWriter domW = new CoreDOMWriter(false);
try{
Element outEl = ((CoreDomRecord)record).getDom();
String xml = domW.toXMLString(outEl);
System.out.println("[XML]:" + xml);
}catch(Exception e){
e.printStackTrace();
return null;
Again , this is the message that I'm receiveing
message-driven bean 'AttuTestReceiverBean' that is not configured with JCA resource adapter must implements the onMessage method of the javax.jms.MessageListener interface
Thanks .

your MessageDrivenBean implements the method:
public Record onMessage(Record record)
but the interface javax.jms.MessageListener has this method:
public void onMessage(Message m)
so you have to change your code.

Similar Messages

  • The FREETALK Connect•Me Home Phone Adapter for Sky...

    Hi all,
    I am seriously considering dropping my landline since I mostly if not only uses my iPhone as my primary device for calls. The problem I have is an alarm system is connected to my land line and requires a way to call the alarm centre in case of an emergency.
    I talk to my alarm service provider for an alternative. They already have the cellular option, but it adds $12/m which is not a big saving... They are working on finding an IP/Internet solution, but it will be also a $4/m.
    I was wondering if I could use the FREETALK Connect•Me Home Phone Adapter for Skype as a solution. From a computer I can call any 1-800 numbers for free, and I really suspect that the alarm centre is a toll free number too. So in theory it could work.
    Can anyone share their experience with the device and suggest if my solution can work or not?
    Thanks

    I use that adapter in my house, it works just as a normal landline would.  There is a slightly longer predial delay when initiating a call (approx 3 second Skype dialing noise), beyond that no real difference.  If the box doesn't lock up, or your Internet doesn't go down it should be rather reliable as a replacement.  Those are worst-case scenarios and I generally don't find myself having to do anything to maintain it.  In any case I have it connected to a power surge strip like I do the rest of my equipment.  Should I need to reset it, I just toggle the switch.

  • Custom Adapter for Inbound Operations never invoked

    Hi,
    I created a custom J2CA Resource Adapter for Inbound operations. I implemented javax.resource.spi.ResourceAdapter interface with all required methods - start(BootstrapContext), endpointActivation(MessageEndpointFactory, ActivationSpec), etc.
    I created the appropriate WSDL file according Adapter Development Cookbook. Below is an excerpt from it:
    <definitions targetNamespace="urn:Adapter" .......>
      <message name="Notification">
        <part name="Notification_Part" element="ns1:Svc"/>
      </message>
      <message name="Header">
        <part name="Header_Part" element="ServiceHeader"/>
      </message>
      <portType name="EventsQueue_ptt">
        <operation name="Dequeue">
          <input message="tns:Notification"/>
        </operation>
      </portType>
      <binding name="NotificationService" type="tns:EventsQueue_ptt">
        <jca:binding/>
        <operation name="Dequeue">
          <jca:operation ActivationSpec="acme.ActivationSpec"/>
          <input>
            <jca:header message="tns:Header" part="Header_Part"/>
          </input>
        </operation>
      </binding>
      <service name="EventsQueue">
        <port name="EventsQueue_pt" binding="tns:NotificationService">
          <jca:address ResourceAdapter="acme.AdapterClass"/>
        </port>
      </service>
    </definitions>I created a BPEL process with a partner link based on this WSDL and linked a Receive activity with it. According Adapter Concepts Guide here is what should happen when the BPEL process is deployed and started:
    - The ResourceAdapter class name and the ActivationSpec parameter are captured in the WSDL extension section of the J2CA inbound interaction WSDL Adapter Integration with BPEL Process Manager Adapter Integration with Oracle Application Server Components 5-7 during design time and made available to BPEL Process Manager and Adapter Framework during run time.
    - An instance of the J2CA 1.5 ResourceAdapter class is created and the Start method of the J2CA ResourceAdapter class is called.
    - Each inbound interaction operation referenced by the BPEL Process Manager processes results in invoking the EndPointActivation method of the J2CA 1.5 ResourceAdapter instance. Adapter Framework creates the ActivationSpec class (Java Bean) based on the ActivationSpec details present in the WSDL extension section of the J2CA inbound interaction and activates the endpoint of the J2CA 1.5 resource adapter.
    The problem is that start(BootstrapContext) and endpointActivation(MessageEndpointFactory, ActivationSpec) seem never to be invoked, the adapter is never initialized and at some point the Receive activity of the BPEL process times-out.
    I put some debug System.out.println statements in these methods, but nothing appeared in the server log.
    I'm using Oracle SOA Suite 10.1.3.1.
    I will be grateful for any suggestions.
    Regards,
    Simeon
    Message was edited by:
    skirov

    user9116351 wrote:
    Hi,
    I have written a custom connector for crud operations to a table in Oracle DB. The custom code class uses oracle.jdbc.OracleDriver which is present in ojdbc14.jar. I have placed this jar in ThirdParty folder of the OIM installation but I am still getting an SQLException while connecting to the DB as my custom code is unable to find the required class. Can someone guide me to some documentation that will help me get over this?
    Thanks,
    SaieshWhich version of OIM you are in? Also you dont need to copy ojdbc14.jar as this exists already in OIM.

  • How does B2B Adapter for Inbound operation for SOA Composite works

    Hai,
    I am new to B2B. can any one share samples or links or doc's on B2B Adapter for inbound operation (receive)?
    Can any one share B2B inbound channel configuration ?

    1. How does the above can be achieved using JMS protocol?Where would you like to pitch-in JMS? You want to receive inbound message at B2B over JMS or between SOA and B2B, you want to use JMS?
    For receiving inbound message at B2B over JMS, please create a non-internal listening channel at B2B. Make sure to set JMS headers -
    http://docs.oracle.com/cd/E23943_01/user.1111/e10229/app_interface.htm#CACDFEAE
    For using JMS between, SOA and B2B, create a JMS channel in Host TP profile and add it in the inbound agreement (for inbound scenario). For outbound scenario, create an internal listening channel and make sure that from back-end, headers mentioned on above link, are being set.
    2. Will SOA Composite having B2B Adapter receive operation has first operation can get triggered automatically or not as soon as EDI----->XML message is found?Yes, it can be triggered. Provided the steps in your another thread.
    3. will B2B Adapter receive operation in SOA Composite will take EDI--------> xml msg as opaque?No, if while modelling B2B adapter, you selected a doc-def otherwise yes.
    Regards,
    Anuj

  • Issue at the time of creation of transfer order for inbound delivery

    Hello,
    I am facing one issue at the time of creation of transfer order for inbound delivery.
    If I create inbound delivery for purchase order with account assignment as 'M' (Ind. cust. w/o KD-CO), inbound delivery is not updated. Also document flow for inbounde delivery s not updated. I can create N number of transfer orders for on inbound delivery. Need help to resolve issue.
    If I create inbound delivery for purchase order with account assignment other than 'M' (Ind. cust. w/o KD-CO), inbound delivery and document flow is updated.
    Thanks and Regards,
    Nikhil

    Hi
    In OMS2 t-code
    for your material type and  plant ,you have to mark value based and qunaity based updation mark
    Regards
    kailas Ugale

  • Does the 4th gen Nano have an adapter for docking stations? Need help!!!!

    I have a philips dock and play docking station and whilst my 1st gen Nano is very happy playing on it the 4th Gen won't even go on properly. Am i not inserting it correctly or are they just not compatible? What i'd really like to know, is there an adapter for the 4th Gen so that i can attach it to the docking station as well?

    Hiya...try this http://www.scosche.com/products/productID/1695
    It's a dock adaptor. Not sure if it works - but frankly, I am just as annoyed as everyone else about the change in connection. I have the original Bose sound dock and the 4th Generation Nano does not work in it.

  • I killed my MBA.  i want to remove the SSD and remove the data.  Is there an adapter for the drive?

    subject pretty much sums it up.
    i need to remove the drive and pull the data from it using another pc.  is there an adapter, usb or otherwise, that fits that drive?
    Is it microsata?
    My mba is late 2011.

    Here is the exact adaper/housing.
    http://eshop.macsales.com/item/OWC/MAU3ENVOY/

  • Troubles with the creation of New Custom Adapter for NW 7.1

    Hi guys !!!
    I have some troubles with the creation of a new custom adapter for NW 7.1. I have followed some pdf and notes, like :
    [Upgrade an SAP NetWeaver PI 7.0 Adapter to SAP NetWeaver PI 7.1|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0667f56-96c7-2b10-0e9a-c40fbd523f4d]
    note : 1004000
    I have all the materials to make the custom Adapter ( like file .sca with all .rar and .sda , like file sample_ra.rar with all the file .java, like all the libs for the projects ) and I have make it !!! But, when I try do deploy it, i recieve a warning that i don't understand, this is the warning :
    S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:C:Users
    maienzaDesktopCreazione del SDAPI71_AF_myFirstCustomAdapter_ver_2.0.sda
         Name:PI71_AF_myFirstCustomAdapter_ver_2.0
         Vendor:sap.com
         Location:SAP AG
         Version:7.1007.20090310105326.0000
         Deploy status:Warning
         Version:NEW
         Description:
              1. Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0.
    No one of the [EJBContainer] containers, which processed it, returned deployed component names.
    The registered containers in this moment were [CTCContainer, com.sap.caf.um.metadata, com.sap.security.ume, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
    Possible reasons :
         1.An AS Java service, which is providing a container, is stopped or not deployed.
         2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
         at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:149)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Result
    Status:Warning
    I have see in the nwa if there are some applications or services that are stopped but all the necessary it's started, just one question : in the pdf for upgrade from 7.0 to 7.1 no one speaks about ejBean or about a creation of it ... it's necessary an ejBean ?? Beacause in the file .sda of the file .sca that i have downloaded there are more of the adapter with ejBean ....
    Antonello

    Hi,
    the adapter metadata it's been created but my service is still stopped; when I try to start it, in the NDWS -> Deploy view -> tab Repositary view, I receive this errors, one after the other, cause I try to start it 3 times and in each time I received 3 differents errors :
    Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.container.DeploymentException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/applicationjars
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.makeStartInitially(ContainerInterfaceImpl.java:771)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.lcm.impl.RemoteLCMImpl.start(RemoteLCMImpl.java:45)
         at com.sap.engine.services.dc.lcm.impl.RemoteLCMImplp4_Skel.dispatch(RemoteLCMImplp4_Skel.java:233)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Caused by: com.sap.engine.services.ejb3.container.ActionException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/applicationjars
         at com.sap.engine.services.ejb3.container.FSMakeFolder.perform(FSMakeFolder.java:48)
         at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
         ... 30 more
    Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.container.DeploymentException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/jars
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.makeStartInitially(ContainerInterfaceImpl.java:771)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.lcm.impl.RemoteLCMImpl.start(RemoteLCMImpl.java:45)
         at com.sap.engine.services.dc.lcm.impl.RemoteLCMImplp4_Skel.dispatch(RemoteLCMImplp4_Skel.java:233)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Caused by: com.sap.engine.services.ejb3.container.ActionException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/jars
         at com.sap.engine.services.ejb3.container.FSMakeFolder.perform(FSMakeFolder.java:48)
         at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
         ... 30 more
    Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0.
    No one of the [EJBContainer] containers, which processed it, returned deployed component names.
    The registered containers in this moment were [CTCContainer, com.sap.caf.um.metadata, com.sap.security.ume, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
    Possible reasons :
         1.An AS Java service, which is providing a container, is stopped or not deployed.
         2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
         at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:149)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.lcm.impl.RemoteLCMImpl.start(RemoteLCMImpl.java:45)
         at com.sap.engine.services.dc.lcm.impl.RemoteLCMImplp4_Skel.dispatch(RemoteLCMImplp4_Skel.java:233)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)

  • How to monitor the alerts(error handling) in seerburger adapter?

    hi,
    is it like normal moniotoring for any scenario..i have to do the monitoring in seeburger adapter.
    any other specific thing i have to take care to do monitoring the alerts (error handling) in seeburger adapter for AS2 and FTP adapters..
    plz give other ways to monitor interfaces for seeburger adapter.
    Regards
    Raja

    Hi Raja,
    All Seeburger adapters have option of some kind of acknowledgement to be sent to the sender or any  partner... u need to check the respective adapter documention....
    for eg: FTP adapter can be configured for Message protocol - FTP-REPORTS
    for sending various types of reports to any Business Partner,,,reports like dispatch report, transmission reports,,....etc
    and for monitoring errors in XI... u can configure alerts as u normally do.....
    *Reward points if useful*
    Regards,
    Sushil.

  • Exception occurred when tried to install Weblogic Adapter for SAP 7.0

    Hi,
              I tried to install current available Weblogic Adapters for SAP 7.0 into weblogic platform 8.1 sp3, I got the following exceptions. Those exceptions can be reproduced when to deploy BEA_SAP_1_0_70.ear into a weblogic integration domain. Based on BEA Weblogic Adapter for SAP installation guide, there should be a new version of adapter for SAP, such as BEA_SAP_8_1.ear, but for some reason, I couldn't find it. The following are error messages, please help.
              Thanks,
              pg
              ------------- error message ------------------
              <Jul 28, 2004 3:01:41 AM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating Deploy task for application BEA_SAP_1_0_70.>
              <Jul 28, 2004 3:01:41 AM EDT> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 2 for the application BEA_SAP_1_0_70.
              weblogic.management.ApplicationException:
              Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 2
              Module: BEA_SAP_1_0.rar Error: Error parsing file at line: 36 column: 27. weblogic.xml.process.XMLParsingException: Error parsing file at line: 36 column: 27. The content of element type "map-config-property" is incomplete, it must match "(map-config-property-name,map-config-property-value)". - with nested exception:
              [org.xml.sax.SAXParseException: The content of element type "map-config-property" is incomplete, it must match "(map-config-property-name,map-config-property-value)".]
              org.xml.sax.SAXParseException: The content of element type "map-config-property" is incomplete, it must match "(map-config-property-name,map-config-property-value)".
              at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1189)
              at weblogic.xml.jaxp.WebLogicParser.parse(WebLogicParser.java:67)
              at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:154)
              at weblogic.connector.deploy.dd.xml.WeblogicRarLoader_Connector10.process(WeblogicRarLoader_Connector10.java:170)
              at weblogic.connector.deploy.dd.xml.DDUtil.processDDFile(DDUtil.java:380)
              at weblogic.connector.deploy.dd.xml.DDUtil.processWeblogicRaDD(DDUtil.java:218)
              at weblogic.connector.deploy.dd.xml.DDUtil.processDDFiles(DDUtil.java:126)
              at weblogic.connector.deploy.dd.xml.DDUtil.getConnectorDescriptor(DDUtil.java:602)
              at weblogic.connector.deploy.dd.xml.DDUtil.getConnectorDescriptor(DDUtil.java:577)
              at weblogic.connector.deploy.ConnectorModule.loadConnectorDescriptors(ConnectorModule.java:693)
              at weblogic.connector.deploy.ConnectorModule.loadDescriptor(ConnectorModule.java:202)
              at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1379)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1204)
              at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    Hello,
              You may have a lot of greif if this is the wrong version of adaptor for 8.1. I too was directed to this EAR file when looking for the 8.1 adaptor. The problem looks like it is in the weblogic-ra.xml file in BEA_SAP_1_0.rar. The some of the xml entries for <map-config-properties> loo incomplete:
              <map-config-property>
              <map-config-property-name>bselocation</map-config-property-name>
              </map-config-property>
              <map-config-property>
              <map-config-property-name>bseeis</map-config-property-name>
              </map-config-property>
              Are missing a value tags.
              You can try adding some dummy ones in order to get passed the SAX exception but you may run into more problems. (I was going to install this my self but never got round to it in the end).
              Good Luck

  • Solution Manager Adapter for HP QC (12)

    Hi,
    As you know, HP has recently launched the version 12 of HP QC.
    We plan to use Solution Manager (7.1) in combination with HP QC (12).
    The only version of Solution Manager Adapter for HP QC I can find on SAP Market place is ST-QCA 100.
    Do you know if there is a newer version of Solution Manager Adapter for HP QC (12) or is it independent of QC version?
    Thanks for your help.
    Regards.

    Hi Priya,
    It is independent of QC Version. I recently integrated ALM 11.52 with Solution Manager SP10 using ST QCA 100 and it worked ust fine. Just make sure with SAP that they support the ALM 12 officially, there might be some changes in ALM 12 which *might* give some problems. SAP as of now did not list ALM 12 in their compatibility matrix;
    I hope they are using the same Enterprise Integration adapter in ALM 12 that they used in 11.52. If so it should work. Give it a try  !
    Regards,
    Vivek

  • FBU Internal Job Queue Full for Synchronous Processing of Print Requests

    Hello All,
    We are getting a lot of errors in system log (SM21) with the
    Error : FBU Internal Job Queue Full for Synchronous Processing of Print Requests
    User :SAPSYS
    MNO:FBU
    =============================================================
    Documentation for system log message FB U :
    If a spool server is to process output requests in the order they were
    created using multiple work processes, the processing of requests for a
    particular device can only run on one work process. To do this an
    internal queue (limited size) is used.
    If too many requests are created for this device too quickly, the work
    process may get overloaded. This is recognized when, as in this case,
    the internal queue is exhausted.
    This can only be solved by reducing the print load or increasing
    processor performance or, if there is a connection problem to the host
    spooler, by improving the transfer of data to the host spooler.
    Increasing the number of spool work processes will not help, as
    requests for one device can only be processed by one work process. If
    processing in order of creation is not required, sequential request
    processing can be deactivated (second page of device configuration in
    Transaction SPAD). This allows several work processes to process
    requests from the same device thus alleviating the bottleneck.
    Enlarging the internal queue will only help if the overload is
    temporary. If the overload is constant, a larger queue will eventually
    also be overloaded.
    ===========================================================
    Can you please tell me how to proceed.
    Best Regards,
    Pratyusha

    Solution is here:
    412065 - Incorrect output sequence of output requests
    Reason and Prerequisites
    The following messages appear in the developer trace (dev_trc) of the SPO processes or in the syslog:
    S  *** ERROR => overflow of internal job queue [rspowunx.c   788]
    Syslog Message FBU:
    Internal job queue for synchronous request processing of output requests full
    The "request processing sequence compliance" on a spool server with several SPO processes only works provided the server-internal job queue (see Note 118057) does not overflow. The size of this request queue is prepared using the rspo/global_shm/job_list profile parameter. The default value is 50 requests. However, if more output requests arrive for the spool server than can be processed (and the internal request queue is full as a result), more SPO processes are used to process the requests (in parallel), and the output sequence of the requests is no longer guaranteed.
    Solution
    Increase the rspo/global_shm/job_list profile parameter to a much larger value. Unfortunately, the value actually required cannot be found by "trial and error" because this queue contains all the incoming output requests on a spool server, not just the "sequence compliant" requests. A practical lower limit for this value represents the maximum sequence-compliant output requests for the above generated output device. If, for example, 1000 documents that should be output in sequence are issued from an application program to an output device, the queue must be able to hold 1000 entries so that it does not overflow if the SPO process processes the requests at a maximum low-speed.

  • Client Adapter for Access table connection

    Were is possible to get just the portion of Oracle Open Client Adapter for ODBC V 6.0.5.35 that enable to establishe a connection with Access table?

    Cisco broadens WLAN offerings
    By John Cox
    Network World Fusion, 11/12/03
    Cisco Wednesday will announce a series of products and product
    improvements to bolster its wireless LAN offerings, including
    additional software that shifts WLAN features into other parts
    of the corporate net.
    The announcement will include, according to a source familiar
    with Cisco's plans:
    * Cisco's first 54M bit/sec 802.11g radios for its access
    points.
    * A new client adapter card that can work with 802.11a, 11b, or
    11g access points.
    * A new version of its IOS network operating system, adapted for
    the model 1100 and 1200 access points.
    * A new software version for the CiscoWorks Wireless LAN
    Solutions Engine, which is a server for administering access
    points.
    Last June, Cisco unveiled a WLAN strategy called Structured
    Wireless-Aware Network (SWAN). The idea behind SWAN is to
    distribute WLAN functions to various devices in the net, as
    appropriate. Cisco officials say some functions are best done on
    access points, and the adaptation of IOS for these devices makes
    them highly programmable, and visible to other Cisco network
    resources, such as network management and network security
    products.
    Other functions have been shifted to the Wireless LAN Solutions
    Engine (WLSE or "willsee" to insiders). Still others will be
    shifted gradually to Cisco's wireline switches and routers, as
    IOS is updated. The first release of "wireless aware" IOS will
    be sometime in 2004, Cisco said.
    For the full story, please go to:
    <http://www.nwfusion.com/news/2003/1112ciswlan.html?nl>

  • IPhone 4S dock connecter quiet while using USA SPEC PA15-INFI ipod adapter for car

    Hello,
    I recently installed the USA SPEC PA15-INFI Ipod connector for my 2004 infiniti g35.  http://usaspec.com/userfiles/editor/file/pa15infi_20100120_webuse.pdf  Essentially it plugs into my satelite radio harness in the trunk and acts as an adapter for an ipod/iphone so you can listen to them on the radio.
    I personally have a 4S iphone and it works great. Great sound.  Full functionality.  However, I tried using my wife's 4S and the radio recognizes it but when you play music it's SUPER quiet.  Almost mute.  It's only on this phone.  In addition to my phone, i tried an ipod and it works great as well.  I callled USA SPEC and they didn't know the problem.  They said this was a problem with my wife's phone specifically and had no suggestions.
    I know my wifes 4S (the problem phone) dock connector works because I just confirmed it on 2 other devices.  Full sound.  No problems.
    Fixes that I have tried:
    Hard reset
    Confirmed mono sound is off
    Confired max volume limiter is off
    reset all settings
    Thanks ahead of time for all of your help!

    I think I know the sound you're referring to, but I had no idea what caused it. I can't recall if it only happenned when charging in the car, but it's bloody irritating.

  • Sample JAVA code using Resource Adapter for RFC Connections

    Hi Java Knowledgeable Ones.
    I have successfully deployed the SAP Netweaver J2ee Engine "Resource Adapter for RFC Connections to ABAP Systems" to my Web Application Server.  Now I need to develop a JAVA application that would utilize this deployed resource adapter.  The resource adapter specifies the SAPClient, UserName, and password.  I am thinking that the JAVA code to invoke this connection would therefore not need to provide this information as it should be available in the resource adapter.
    Do you have sample code that you could send to me showing how to do this?
    Thanks,
    Kevin

    Hi Kevin,
    this is actually no good style! You should not open the connection with the adaptor knowing the password. Usually it should work via a connection that uses only basic rights  and the user has already authenticated and is using his security ticket.
    For security handling see:
    http://help.sap.com/saphelp_nw04/helpdata/en/61/f8bc3d52f39d33e10000000a11405a/frameset.htm
    Regards,
    Benny

Maybe you are looking for