IWay JAM (Java Adapter for Mainframe)

iWay JAM (Java Adapter for Mainframe) is certified to work with Weblogic 10.2?
http://egeneration.bea.com/iwaydocs/iway55/5.1/JAM/wls_versions.html

Glen,
          no, jam gateway to the crm communication is in cleartext.
          -richard

Similar Messages

  • Java Adapter for Mainframe egen bug who do I contact ?

    Hi I could not find a newsgroup or a support link for the JAM product. I wanted
    to raise a couple of bugs since sometimes the xml schema (xsd) generated is malformed.
    Can someone point me in the right direction or advise as to how to go about this
    ? Thanks in advance.
    Peter

    It was not and has not been a pleasant experience these past few days. I've followed the directions and am following you, once you follow me back we can hopefully work this out.
    Thank you.ArnettH_VZW

  • Resource Adapter for Mainframes!

              Hi,
              Is there any resource adapter available for Mainframes?
              Thanks,
              Thangamani
              

              List of certified resource adapters for MF (VSAM, CICS, ADABAS, Natural, IMS etc)
              can be found in http://www.bea.com/products/servers_integration/adaptermatrix.shtml
              Esti
              "Stefan Krieger" <[email protected]> wrote:
              >You can download a resource adapter for IBM CICS at
              >http://www.comporsys.com.
              >
              >Enjoy,
              >Stefan
              >
              >Thangamani Vaiyapuri <[email protected]> schrieb in im Newsbeitrag:
              >3b52d3f3$[email protected]..
              >>
              >> Hi,
              >>
              >> Is there any resource adapter available for Mainframes?
              >>
              >> Thanks,
              >> Thangamani
              >
              >
              

  • Java Adapter Compile Error - Missing Libraries

    I am trying to convert my project from being deployed on Flex Data Services 2 To LiveCycle Data Services. I dont know very much about java and have hit a snag when trying to recompile my custom java adaptor.
    It compiles fine under a FDS2 project, but when compiled under a LCDS deployment on JRun, Eclipse gives me the following error when trying to compile:
    Project PTSChat_Java is missing required library: lib/commons-codec.jar
    Project PTSChat_Java is missing required library: lib/commons-httpclient.jar
    The project cannot be built until build path errors are resolved
    It appears that the libraries have been renamed to commons-codec-1.3.jar & commons-httpclient-3.0.1.jar in LCDS, but I am not sure where to update these references? They are not direct library imports in my java code.
    As a shot in the dark, I tried just copying the old FDS2 libraries back over to the WEB-INF\lib\ DIR since there are named differently. It resolved the missing library error, but then I got a compile error with service cannot be resolved in references to my MessageService msgService = (MessageService) service; java code. I quickly realized this is not the correct path to head down.
    Does anyone have any clues what I may be doing wrong? Any help is much appreciated.
    Thanks!

    I resovled the problems I was having.
    I was able to figure out how to change the library linking in eclipse and switched the commons-codec-1.3.jar & commons-httpclient-3.0.1.jar in the place of commons-codec.jar & commons-httpclient.jar libraries previously used with the project (properties:libraries).
    I was not able to correct the service cannot be resolved. Everything I did kept crashing and dropping my connection tot he channel. I ended up just switching the code in my java adapter from:
    MessageService msgService = (MessageService) service
    to
    MessageBroker broker = MessageBroker.getMessageBroker(null);
    MessageService msgService = (MessageService) broker.getService("message-service");
    This appears to be working as desired for my use of the java adapter for the session management & logging. I am not really certain why the "service" became undefined between FDS2 & LCDS, something must have been depreciated or changed around.

  • Problem about Iway Adapter for SAP

    My Problem is when I updated the data in SAP system, Iway adapter also updated but in my application did not update this data at all, so I needed to restart Weblogic server and then it was updated ka. Thus, whenever I changed the data in SAP, I need to stop and start Weblogic server again and again in order to make it update na ka. I don’t know what the problem is about the server and How I can get over it. Can somebody give me any suggestion?

    Adapters on WebLogic 7.0 are very old and are application view based adapters.
    Wanted to know what version of WebLogic and iWay adapter will support the integration with SAP ECC 6.0?It depends on how you plan to use the Adapters (ie with OSB or SOA Suite).
    OSB 10.3.1--http://www.oracle.com/technology/products/soa/service-bus/collateral/documentation.html
    http://www.oracle.com/technology/software/products/osb/index.html
    http://download.oracle.com/otndocs/tech/products/integration/service-bus/SAPDEMO.zip
    SOA Suite 11g- -http://download.oracle.com/docs/cd/E15523_01/doc.1111/e17057/toc.htm
    iWay is the OEM for both adapters.
    Also is there any recommended upgrade / migration plan defined for such a scenario? Adapter on WebLogic 7.0 are very old and there is no migration path.
    Any compatibility issues to be aware of. Please provide any details / references related to thisNothing I'm aware of. To avail connectivity to SAP ECC6.0, you will have to use latest weblogic for which the adapters are certified.
    Manoj

  • Using Tuxedo Mainframe adapter for SNA with OSB

    Hi,
    Can we use the Oracle Tuxedo mainframe adapter for SNA with the OSB?
    If yes then how?

    Hi Priyanka,
    The Tuxedo Mainframe Adapters are separably licensed products and not included in the Tuxedo kits. I'm not certain the mainframe adapters are yet available for 10gR3 (I'm checking on this), and for whatever reason the latest version I can find for download is the 9.1 version that can be downloaded from eDelivery.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • Installable for Oracle Tuxedo Mainframe Adapter for TCP (CICS)

    Hi,
    Could anyone please help me to find the installable for "Oracle Tuxedo Mainframe Adapter for TCP (CICS)", does this comes with the Tuxedo 10g installable or is it a separate plug-in that I need to download and install.
    Regards,
    Priyanka

    Hi Priyanka,
    The Tuxedo Mainframe Adapters are separably licensed products and not included in the Tuxedo kits. I'm not certain the mainframe adapters are yet available for 10gR3 (I'm checking on this), and for whatever reason the latest version I can find for download is the 9.1 version that can be downloaded from eDelivery.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • Is there any Java Adapter SDK for building iIS adapters?

     

    If you're using iIS 3.0, check out XML Adapter Designer 2.0.
    http://docs.iplanet.com/docs/manuals/xad.html
    This tool will assist you in building java adapters for iIS.

  • 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

  • Archiving: experience with Oracle's Archive Adapter for SAP

    All,
    Does anyone have experience to share about Oracle's "Content Database Archive Adapter for SAP Applications"?
    Thanks
    Guenther

    Sasi,
    There is a new MySAP adapter with 10.13.1 and above to support ECC 6.0. Please see the following section in the 10.1.3.1 adapter release notes:
    12.4.1 MySAP ERP Versions and APIs
    The following MySAP ERP platforms are supported by OracleAS Adapter for MySAP
    ERP:
    ■ SAP R/3 Enterprise 47x100
    ■ SAP R/3 Enterprise 47x200
    ■ MySAP ERP Central Component (ECC) 5.0, deployed on SAP NetWeaver 2004
    ■ MySAP ERP Central Component (ECC) 6.0, deployed on SAP NetWeaver 2004s
    ■ SAP Java Connector (SAP JCo) Version 2.18.
    For the current release status of the SAP Java Connector, refer to SAP Note #549268
    in the SAP Service Marketplace.
    Release versions may vary by product component. In addition, SAP functions may
    vary by SAP product version and support package.
    Note: The OracleAS Adapter for MySAP ERP supports only the versions listed above.
    It is not recommended to use the OracleAS Adapter for MySAP ERP with older
    versions of SAP R/3. If you plan to use the adapter with older versions of SAP R/3 for
    example SAP R/3 4.6C, prior approval from iWay Software Product Management is
    required.

  • Oracle Adapter for SAP that supports Integration with SAP 6.0??

    Hi,
    I am working currently with Oracle Adapter for SAP with SAP 4.6.
    But my company is looking for upgrading the Enterprise SAP system to 6.0.
    Do we have Oracle Adapter for SAP that supports SAP 6.0? Please let me know if anyone has already worked on this?
    Thanks,
    Sasi Bhushan

    Sasi,
    There is a new MySAP adapter with 10.13.1 and above to support ECC 6.0. Please see the following section in the 10.1.3.1 adapter release notes:
    12.4.1 MySAP ERP Versions and APIs
    The following MySAP ERP platforms are supported by OracleAS Adapter for MySAP
    ERP:
    ■ SAP R/3 Enterprise 47x100
    ■ SAP R/3 Enterprise 47x200
    ■ MySAP ERP Central Component (ECC) 5.0, deployed on SAP NetWeaver 2004
    ■ MySAP ERP Central Component (ECC) 6.0, deployed on SAP NetWeaver 2004s
    ■ SAP Java Connector (SAP JCo) Version 2.18.
    For the current release status of the SAP Java Connector, refer to SAP Note #549268
    in the SAP Service Marketplace.
    Release versions may vary by product component. In addition, SAP functions may
    vary by SAP product version and support package.
    Note: The OracleAS Adapter for MySAP ERP supports only the versions listed above.
    It is not recommended to use the OracleAS Adapter for MySAP ERP with older
    versions of SAP R/3. If you plan to use the adapter with older versions of SAP R/3 for
    example SAP R/3 4.6C, prior approval from iWay Software Product Management is
    required.

  • Using DB Adapter for MS SQL Server 2005  SP in OSB 11g.

    Hi All,
    I have a requirement to create a DB Adapter for MS SQL Server Stored Procedure in JDeveloper and export the Adapter file to OSB 11g. I have Created the Adapter and imported it into OSB 11g successfully. Created the Datasource and Connection pool also in console.
    The problem is while trying to execute the created business Service, I am getting the error as below,
    <Oct 26, 2012 12:20:25 PM IST> <Error> <JCATransport> <BEA-381967> <Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/Test/CheckAppID/WL_Driver/CheckAppId_WL_Driver [ CheckAppId_WL_Driver_ptt::CheckAppId_WL_Driver(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'CheckAppId_WL_Driver' failed due to: Unimplemented string conversion.
    Conversion of JDBC type to String is not supported.
    An attempt was made to convert a Java object to String using an unsupported JDBC type: .
    ; nested exception is:
         BINDING.JCA-11804
    Unimplemented string conversion.
    My XSD is ,
    <element name="InputParameters">
    <complexType>
    <sequence>
    <element name="application_id" type="int" db:index="1" db:type="INT" minOccurs="0" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <element name="OutputParameters">
    <complexType>
    <sequence>
    <element name="RowSet0" type="db:RowSet0_RowSet" db:type="RowSet0" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
    <element name="RowSet1" type="db:RowSet1_RowSet" db:type="RowSet1" minOccurs="0" maxOccurs="unbounded" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <complexType name="RowSet1_RowSet">
    <sequence>
    <element name="RowSet1_Row" minOccurs="0" maxOccurs="unbounded">
    <complexType>
    <sequence>
    <element name="cde" type="int" db:type="INT" minOccurs="0" nillable="true"/>
    <element name="msg" db:type="NVARCHAR" minOccurs="0" nillable="true">
    <simpleType>
    <restriction base="string">
    <maxLength value="255"/>
    </restriction>
    </simpleType>
    </element>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    <complexType name="RowSet0_RowSet">
    <sequence>
    <element name="RowSet0_Row" minOccurs="0" maxOccurs="unbounded">
    <complexType>
    <sequence>
    <element name="aaa" type="boolean" db:type="BIT" minOccurs="0" nillable="true"/>
    <element name="bbb" db:type="NVARCHAR" minOccurs="0" nillable="true">
    <simpleType>
    <restriction base="string">
    <maxLength value="10"/>
    </restriction>
    </simpleType>
    </element>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    I don't know why there is a datatype conversion error.
    Help me in resolving this.
    Regards,
    Nataraj R.

    Hi,
    I believe NVARCHAR is an unsupported type...
    The following document lists the supported data types for SQL Server stored procedures and functions... NVARCHAR is not in the list... :-(
    http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/adptr_db.htm#CHDEBEEE
    Hope this helps...
    Cheers,
    Vlad

  • Error in Pre-Pop Adapter for AD using ResourceObjectDefinition Mapping

    Hi
    I have a PRe-pop adapter for Org name in AD -
    One of the variables is ResourceObjectDefintion. However OIM is not able to map it to the right object name and throws the below error -
    cAdapterDataMap/getResourceObjectInfo encounter some problems: Error retrieving user info: Object Name
    Class/Method: tcAdapterDataMap/getResourceObjectInfo encounter some problems: Column 'AD XXX' not found
    com.thortech.xl.dataaccess.tcDataSetException: Column 'AD XXX' not found
         at com.thortech.xl.dataaccess.tcDataSet.getColumnIndex(Unknown Source)
         at com.thortech.xl.dataaccess.tcDataSet.getDataType(Unknown Source)
         at com.thortech.xl.dataobj.util.tcAdapterDataMap.getProcessResourceObjectInfo(Unknown Source)
         at com.thortech.xl.dataobj.util.*tcAdapterDataMap.getResourceObjectInfo*(Unknown Source)
         at com.thortech.xl.dataobj.rulegenerators.tcBaseRuleGenerator.getRunTimeValue(Unknown Source)
         at com.thortech.xl.dataobj.rulegenerators.adpADPOPULATEMANAGEROU.implementation(adpADPOPULATEMANAGEROU.java:56)
         at com.thortech.xl.dataobj.rulegenerators.tcBaseRuleGenerator.run(Unknown Source)
         at com.thortech.xl.dataobj.rulegenerators.tcAdapterExecuter.executeRuleGenerators(Unknown Source)
         at com.thortech.xl.dataobj.util.tcPrePopulateUtility.setDataFromAdapter(Unknown Source)
         at com.thortech.xl.dataobj.util.tcPrePopulateUtility.prePopulate(Unknown Source)
         at com.thortech.xl.ejb.beansimpl.tcFormInstanceOperationsBean.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.beansimpl.tcFormInstanceOperationsBean.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.beans.tcFormInstanceOperationsSession.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.interfaces.EJSRemoteStatelesstcFormInstanceOperations_3fa3c79b.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.interfaces._tcFormInstanceOperations_Stub.prepopulateProcessForm(_tcFormInstanceOperations_Stub.java:1963)
         at Thor.API.Operations.tcFormInstanceOperationsClient.prepopulateProcessForm(Unknown Source)
    at com.thortech.xl.dataobj.util.tcAdapterDataMap.getResourceObjectInfo(Unknown Source)
         at com.thortech.xl.dataobj.rulegenerators.tcBaseRuleGenerator.getRunTimeValue(Unknown Source)
         at com.thortech.xl.dataobj.rulegenerators.adpADPOPULATEMANAGEROU.implementation(adpADPOPULATEMANAGEROU.java:56)
         at com.thortech.xl.dataobj.rulegenerators.tcBaseRuleGenerator.run(Unknown Source)
         at com.thortech.xl.dataobj.rulegenerators.tcAdapterExecuter.executeRuleGenerators(Unknown Source)
         at com.thortech.xl.dataobj.util.tcPrePopulateUtility.setDataFromAdapter(Unknown Source)
         at com.thortech.xl.dataobj.util.tcPrePopulateUtility.prePopulate(Unknown Source)
         at com.thortech.xl.ejb.beansimpl.tcFormInstanceOperationsBean.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.beansimpl.tcFormInstanceOperationsBean.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.beans.tcFormInstanceOperationsSession.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.interfaces.EJSRemoteStatelesstcFormInstanceOperations_3fa3c79b.prepopulateProcessForm(Unknown Source)
         at com.thortech.xl.ejb.interfaces._tcFormInstanceOperations_Stub.prepopulateProcessForm(_tcFormInstanceOperations_Stub.java:1963)
         at Thor.API.Operations.tcFormInstanceOperationsClient.prepopulateProcessForm(Unknown Source)
    Thanks

    - Verify that the AD XXX RO exists in the system , if its there , then re do the mappings once more .
    I did the same and it worked for me
    Thanks
    Suren

  • 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)

  • FTP adapter for Oracle Service Bus  - retrieve file by dynamic file name.

    Hi
    I am newbie in OSB. I try to use FTP transport in Workshop, it must fill in "Prefix" and "Suffix" for destination file name.
    But for us, the file name is sent by external systems.
    The workflow is:
    1. External system call our proxy services.
    2. Proxy service get file name from SOAP message.
    3. Proxy Service get the file from FTP server.
    4. The file send to Business services.
    Any suggestions to implement about workflows?

    Let me first put here what I understand about the flow:
    External Sytem -->(filename)--> OSB HTTP PS --> (1) --> OSB FTP BS --> Read file based on filename
    |--> (2) --> send file ontent to another system or return to the original system
    If that is the flow, then I beileve ther is no straight forward way to implement it in OSB.
    OSB FTP BS will only write a file to FTP Location.
    If you create a JCA FTP Adapter for reading the file, then you can use it only to create a Proxy Service, and that proxy will not pick up the file when called from another service but only when a file is put on the source FTP location.
    So, to implement the solution you will need to use Java Callout to a class which has code written to accept the file name as input, read the file from an FTP location and return the file content.
    This is my understanding of how it is, may be there is another way to implement this or in fact may be the latest version of OSB 11.1.1.4 or 11.1.1.5 JCA adapter does support read operation within a flow instead of just at the start of the flow.

Maybe you are looking for