Wsimport & custom Adapter package names

I'm working with JAX-WS (2.1.7)
How do you change the package name for the generated Adapter classes. They are currently generated in package "org.w3._2001.xmlschema"
I can do this with XJC as per [https://jaxb.dev.java.net/guide/Customizing_Java_packages.html#Tip__get_rid_of_the_org_w3__2001_xmlschema_package]
How do i do the same with wsimport ? For the above customization to work, i need to import the dummy XSD (XMLSchema.xsd) into my WSDL....very ugly.
Is there a way to specify multiple schema files as input ( similar to child <schema> tags in XJC ??) without having to import.
Thanks,
Ram.

Hi Pankaj,
Refer these links to get the jar libraries for the module development:
http://wiki.sdn.sap.com/wiki/display/XI/XIlibrariesfor+development
http://wiki.sdn.sap.com/wiki/display/XI/WheretogetthelibrariesforXI+development
And to add libraries to the NWDS Java Build path refer this guide to adapter development:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa?quicklink=index&overridelayout=true
Regards,
Aravind

Similar Messages

  • Code to retrive the sender and receiver interface names using custome adapter module

    Hello Team,
    I want to develop an custom adapter module which could retrieve the names of the sender and receiver interfaces of the scenario and for that i am trying to use com.sap.aii.af.service.administration.api.monitoring.ProcessContextFactory.ParamSet but i don't know whether this API will support or not and also i don't know how to develop the code using this API so please suggest me some code for it so that i could retrieve the names.
    Thanks you all in advance.
    Regards,
    Avinash.   

    Hi,
    Just ASMA setting will do the needful. Are you planning to rename your target file name. If yes then only you will require UDF.
    Update: Since your directory name will be taken from source file name then you have to use mapping for this, else it will not be possible.
    I don't know if creating a new module for this will help you solve the issue, but in that case rather creating adapter module, mapping will be easier.
    Regards,
    Sarvesh
    Edited by: Sarvesh Singh on Dec 7, 2009 3:04 PM

  • Custom Adapter Development - Some bugs is the development process

    hi
    I'm working through the steps in the document "BEA WebLogic Integration -
    Developing Adapters" - Chapter 4 Creating a Custom Environment.
    I'm using the version of WLS 8.1.1 on the dev2dev trial CD.
    I've encountered the following errors which I think are bugs and should be
    fixed:
    =========================================================
    1. Incorrect naming of a properties file
    =============================
    Step 2. Rebuild the Tree - when running "ant release" immediately after
    generation, the build fails with the following error:
    Buildfile: build.xml
    packages:
    [echo] Building NICOLSON_SAMPLE_1_0...
    generate_web_descriptors:
    [java] Substituting web descriptor variable: display-name
    [java] Substituting web descriptor variable: version
    [java] Substituting web descriptor variable: extra-jsp-servlets
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: request-handler-class
    [java] Substituting web descriptor variable: debug-setting
    [java] Substituting web descriptor variable: extra-jsp-servlet-mappings
    [java] Generated web.xml as:
    C:\software\devtools\bea\weblogic81\integratio
    n\adapters\nicolson\project\..\..\..\adapters\nicolson\src\war\WEB-INF\web.x
    ml
    merge_properties:
    [echo] Merging NICOLSON_SAMPLE_1_0-base.properties and ADK.properties
    [echo]
    props_dir=C:\software\devtools\bea\weblogic81\integration\adapters\n
    icolson\project/../../../adapters/nicolson/src
    WLI_HOME=C:\software\devtools\bea
    \weblogic81\integration\adapters\utils\ant/../../..
    [concat] File
    C:\software\devtools\bea\weblogic81\integration\adapters\nicols
    on\src\NICOLSON_SAMPLE_1_0-base.properties does not exist.
    BUILD FAILED
    java.lang.NullPointerException
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:103)
    at java.io.FileInputStream.<init>(FileInputStream.java:66)
    at org.apache.tools.ant.taskdefs.Concat.catFiles(Concat.java:353)
    at org.apache.tools.ant.taskdefs.Concat.execute(Concat.java:271)
    at org.apache.tools.ant.Task.perform(Task.java:317)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:334)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
    at org.apache.tools.ant.Task.perform(Task.java:317)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:334)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
    at org.apache.tools.ant.Main.runBuild(Main.java:610)
    at org.apache.tools.ant.Main.start(Main.java:196)
    at org.apache.tools.ant.Main.main(Main.java:235)
    Total time: 1 second
    This is occuring for because Step 1. Execute GenerateAdapterTemplate is
    generating an incorrectly named properties file in the src directory.
    i.e. it is generating NICOLSON_SAMPLE_1_0.properties when it should
    generate NICOLSON_SAMPLE_1_0-base.properties
    On correcting this problem, the next error will occur
    ==================================================
    2. Missing junit.jar in wli_home/lib
    ==========================
    Buildfile: build.xml
    packages:
    [echo] Building NICOLSON_GENERIC_1_0...
    generate_web_descriptors:
    [java] Substituting web descriptor variable: display-name
    [java] Substituting web descriptor variable: version
    [java] Substituting web descriptor variable: extra-jsp-servlets
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: request-handler-class
    [java] Substituting web descriptor variable: debug-setting
    [java] Substituting web descriptor variable: extra-jsp-servlet-mappings
    [java] Generated web.xml as:
    C:\software\devtools\bea\weblogic81\integratio
    n\adapters\sal\project\..\..\..\adapters\sal\src\war\WEB-INF\web.xml
    merge_properties:
    [echo] Merging NICOLSON_GENERIC_1_0-base.properties and ADK.properties
    [echo]
    props_dir=C:\software\devtools\bea\weblogic81\integration\adapters\s
    al\project/../../../adapters/sal/src
    WLI_HOME=C:\software\devtools\bea\weblogic8
    1\integration\adapters\utils\ant/../../..
    [javac] Compiling 15 source files
    [javac]
    C:\software\devtools\bea\weblogic81\integration\adapters\sal\src\com
    \nicolson\base\integration\sample\jca\bea\sal\spi\NonManagedScenarioTestCase
    .jav
    a:9: package junit.framework does not exist
    [javac] import junit.framework.*;
    [javac] ^
    [javac]
    C:\software\devtools\bea\weblogic81\integration\adapters\sal\src\com
    \nicolson\base\integration\sample\jca\bea\sal\spi\NonManagedScenarioTestCase
    .jav
    a:20: cannot resolve symbol
    There was no junit.jar in WLI_HOME/lib. The problem disappears once this jar
    is added.
    ===============================================================
    3. Class not found error when running tests using "ant test"
    ==========================================
    Buildfile: build.xml
    packages:
    [echo] Building NICOLSON_SAMPLE_1_0...
    generate_web_descriptors:
    [java] Substituting web descriptor variable: display-name
    [java] Substituting web descriptor variable: version
    [java] Substituting web descriptor variable: extra-jsp-servlets
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: request-handler-class
    [java] Substituting web descriptor variable: debug-setting
    [java] Substituting web descriptor variable: extra-jsp-servlet-mappings
    [java] Generated web.xml as:
    C:\software\devtools\bea\weblogic81\integratio
    n\adapters\nicolson\project\..\..\..\adapters\nicolson\src\war\WEB-INF\web.x
    ml
    merge_properties:
    [echo] Merging NICOLSON_SAMPLE_1_0-base.properties and ADK.properties
    [echo]
    props_dir=C:\software\devtools\bea\weblogic81\integration\adapters\n
    icolson\project/../../../adapters/nicolson/src
    WLI_HOME=C:\software\devtools\bea
    \weblogic81\integration\adapters\utils\ant/../../..
    test:
    [java] <3/10/2003 10:40:37 AM EST> <Debug> <NICOLSON_SAMPLE_1_0>
    <000000> <
    added new configuration from file 'NICOLSON_SAMPLE_1_0.xml' with root
    category '
    NICOLSON_SAMPLE_1_0' to category hierarchy for locale 'en_US'>
    [java] Loading
    com.nicolson.integration.bea.sample.spi.NonManagedScenarioTe
    stCase for inclusion in the test suite
    [java] Loading
    com.nicolson.integration.bea.sample.event.OfflineEventGenera
    torTestCase for inclusion in the test suite
    [java] EXCEPTION: attempted to load
    com.nicolson.integration.bea.sample.eve
    nt.OfflineEventGeneratorTestCase
    [java] java.lang.ClassNotFoundException:
    com.nicolson.integration.bea.sampl
    e.event.OfflineEventGeneratorTestCase
    [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
    [java] at java.security.AccessController.doPrivileged(Native
    Method)
    [java] at
    java.net.URLClassLoader.findClass(URLClassLoader.java:186)
    [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    [java] at
    sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:265)
    [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
    [java] at
    com.bea.adapter.test.TestHarness.suite(TestHarness.java:61)
    [java] at
    com.bea.adapter.test.TestHarness.main(TestHarness.java:96)
    [java] java.lang.NoSuchMethodError:
    junit.textui.TestRunner.run(Ljunit/fram
    ework/Test;)V
    [java] at
    com.bea.adapter.test.TestHarness.main(TestHarness.java:96)
    [java] Exception in thread "main"
    [java] Java Result: 1
    BUILD SUCCESSFUL
    Total time: 2 seconds
    The missing test case is being explicitly excluded from the build:
    <javac deprecation='true' debug='true'>
    <classpath refid='CLASSPATH'/>
    <src path="${SRC_DIR}"/>
    <include name="**/*.java"/>
    <exclude
    name="com/nicolson/integration/bea/sample/event/OfflineEventGeneratorTestCas
    e.java" />
    <exclude name="war/jsp_servlet/**"/>
    </javac>
    If it is included, the following compile error occurs...
    C:\software\devtools\bea\weblogic81\integration\adapters\nicolson\project>an
    t re
    lease
    Buildfile: build.xml
    packages:
    [echo] Building NICOLSON_SAMPLE_1_0...
    generate_web_descriptors:
    [java] Substituting web descriptor variable: display-name
    [java] Substituting web descriptor variable: version
    [java] Substituting web descriptor variable: extra-jsp-servlets
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: adapter-logical-name
    [java] Substituting web descriptor variable: request-handler-class
    [java] Substituting web descriptor variable: debug-setting
    [java] Substituting web descriptor variable: extra-jsp-servlet-mappings
    [java] Generated web.xml as:
    C:\software\devtools\bea\weblogic81\integratio
    n\adapters\nicolson\project\..\..\..\adapters\nicolson\src\war\WEB-INF\web.x
    ml
    merge_properties:
    [echo] Merging NICOLSON_SAMPLE_1_0-base.properties and ADK.properties
    [echo]
    props_dir=C:\software\devtools\bea\weblogic81\integration\adapters\n
    icolson\project/../../../adapters/nicolson/src
    WLI_HOME=C:\software\devtools\bea
    \weblogic81\integration\adapters\utils\ant/../../..
    [javac] Compiling 1 source file
    [javac]
    C:\software\devtools\bea\weblogic81\integration\adapters\nicolson\sr
    c\com\nicolson\integration\bea\sample\event\OfflineEventGeneratorTestCase.ja
    va:1
    62:
    com.nicolson.integration.bea.sample.event.OfflineEventGeneratorTestCase.Test
    EventRouter should be declared abstract; it does not define getName() in
    com.nic
    olson.integration.bea.sample.event.OfflineEventGeneratorTestCase.TestEventRo
    uter
    [javac] class TestEventRouter
    [javac] ^
    [javac] 1 error
    BUILD FAILED
    file:C:/software/devtools/bea/weblogic81/integration/adapters/nicolson/project/b
    uild.xml:340: Compile failed; see the compiler error output for details.
    Total time: 2 seconds
    This is because an inner class used in the test case does not fully
    implement methods of the interface it realizes.
    In fact it is missing a number of methods.
    =========================================================
    Just as well I'm only doing a personal eval :)
    Regards
    Jim Nicolson

    Dear Aandi,
    I am really thankful to you for this. I will suggest this to the business and then they can contact adobe for this. Thanking you once again for providing me with all the valueable info. You have been instrumental in helping me out in my project.
    Best Regards,
    Deepak Goyal

  • How to invoke a custom adapter from a BPEL process

    Hi guys,
    I've implemented a custom outbound adapter and deployed successfully on Weblogic V.10.3.4.
    My current installation also consists of Oracle SOA Suite 11g / JDeveloper 11g (11.1.1.4.0)
    In the Weblogic administrator's console,
    *1.* I navigated to:
    Summary of Deployments -> AdapterName -> Configuration -> Outbound Connection Pools
    *2.* Selected: javax.resource.cci.ConnectionFactory and added new JNDI name for Outbound Connection Instance: "*eis/HelloWorld*"
    My task is to invoke the custom adapter from a BPEL process.
    I altered the customAdapter-config.xml so as to be able to use custom adapter wizard from JDeveloper's "Service Adapters" palette,
    and fullfilled the custom adapter wizard's fields accordingly. The 3rd step of the wizard requires Connection Information.
    I added: "*eis/HelloWorld*" in the "*Connection Factory Location*" field.
    Deployed BPEL process successfully, but testing failed due to binding.jca-12510 error:
    "The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/HelloWorld'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/HelloWorld. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server "I tried to apply (just for testing) "eis/FileAdapter" in the "Connection Factory Location" field of the custom adapter wizard,
    and BPEL successfully invoked the adapter.
    Any ideas ?
    Thanks,
    George

    George, What deployment do you have this associated with?
    - D.J.

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

  • Unable to deploy custom adapter module in PI 7.31

    Hi pros,
    I created a custom adapter module to split some complex input files to multiple messages. We use a SAP PO 7.31 java-only installation. I followed this document to create my adapter module:
    How to Create Modules for the JEE Adapter Engine
    I know it is for PI 7.1 but a colleague of mine said that he was able to create a running adapter module for PI 7.3 following the guide. I created the following projects:
    EAR project references the EJB project:
    Project facet of the EJBproject:
    ejb-jar.xml config:
    application-j2ee-engine.xml (in EAR project):
    When I try to deploy my module, I get the following error:
    Java version:
    NWDS version:
    Any hint is appreciated! What can be wrong? What can I check again?
    THANKS!
    Message was edited by: Stefan Münchow

    I am not sure if the version is the problem. We have PI 7.31, support package 14, patch level 0 and NWDS 7.31 support package 12, patch level 4. The version of NWDS is lower than the version of the PI. According to Note 1599298 the error occurs when the NWDS is higher than the one of PI. Besides, we are able to deploy BPMN processes with the same NWDS to the same server.
    This is the exact exception trace shown in NWDS:
    com.sap.ide.eclipse.sdm.deploy.DeploymentException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:110)
    ------------- Nested exception -------------------
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
    at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
    at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:80)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
    at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
    at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
    at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
    at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
    at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
    ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/DP2/J64/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/213/SplitArticleFileModule_EAR.ear] failed
    at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
    at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
    ... 11 more
    Caused by: com.sap.engine.services.deploy.container.rtgen.GenerationException: Open failed for '/usr/sap/DP2/J64/j2ee/cluster/server0/temp/deploy/SplitArticleFileModule_EAR.ear1422275742985/com.sap.aii.utilxi.server.jar' with fd 218 returning message 'couldn't find 'END' tag' and errno 0 after trying cache.
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.createSingleModule(WebServicesGenerator.java:100)
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.generate(WebServicesGenerator.java:54)
    at com.sap.engine.services.deploy.container.rtgen.AnnotationsSupportingGenerator.generate(AnnotationsSupportingGenerator.java:27)
    at com.sap.engine.services.deploy.ear.jar.moduledetect.GeneratorWrapper.generate(GeneratorWrapper.java:43)
    at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generate(ModuleGeneratorTool.java:110)
    at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generateOverExistingModules(ModuleGeneratorTool.java:97)
    at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generateModules(ModuleGeneratorTool.java:80)
    at com.sap.engine.services.deploy.ear.jar.EARReader.read(EARReader.java:240)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.prepareNewDeploymentInfo(DeployUtilTransaction.java:217)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:199)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
    ... 12 more
    Caused by: java.util.zip.ZipException: Open failed for '/usr/sap/DP2/J64/j2ee/cluster/server0/temp/deploy/SplitArticleFileModule_EAR.ear1422275742985/com.sap.aii.utilxi.server.jar' with fd 218 returning message 'couldn't find 'END' tag' and errno 0 after trying cache.
    at java.util.zip.ZipFile.open(Native Method)
    at java.util.zip.ZipFile.<init>(ZipFile.java:154)
    at java.util.jar.JarFile.<init>(JarFile.java:141)
    at java.util.jar.JarFile.<init>(JarFile.java:105)
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesSupportHandlerImpl.generateWebSupport(WebServicesSupportHandlerImpl.java:79)
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.createSingleModule(WebServicesGenerator.java:69)
    ... 26 more
    Maybe the used jar files could be the problem?

  • AP to GL Transfer: How to have a custom Journal Header name in GL.

    Hi,
    Does any one know how to have a custom Journal Header name while transferring the Journals from AP to GL?
    Assume that I am transferring the Journals which belongs to a Single Invoice from AP to GL. When these Journals are transferred from AP to GL, Oracle will create a Journal Header with the default naming convention. The Oracle generated Header name will be as shown below.
    *123456 Purchase Invoices USD*. Where 123456 is AE_HEADER_ID and USD is the Invoice Currency code.
    Our requirement is, we want the Journal Header name something like *"Hello World"+TIMESTAMP*, where TIMESTAMP is the date when the user has ran the AP to GL transfer program.
    I know that when building the AAD(Application Accounting Definition) we can define the Journal Header descriptions and Journal Lines descriptions. But, I did not see any setup option to have the custom Journal Header name in GL.
    Any suggestions on this issue are highly appreciated.
    Advanced Thanks,
    Lokesh.

    Hi Lokesh,
    The best way to have a custom journal header name is using hook package.
    When data move from XLA to GL, every time it creates a new dynamic table as GL_INTERFACE table but the name is different (XLA_GLT_XXXXX).
    This table information stores in 'gl_interface_control' table but after use the record has deleted from 'gl_interface_control'.
    So we can't see table information after finishing create accounting program.
    What the modification you will made in this table it will affect GL base table. So to made custom journal header name, we need to change Reference4 column of dynamic table.
    Here is the code to get the table name and through procedure you can update the Reference4 column.
    FUNCTION pre_module_hook(run_id IN NUMBER,
                   errbuf IN OUT NOCOPY VARCHAR2) RETURN BOOLEAN IS
    chr_errbuf varchar2(50);
    chr_retcode varchar2(50);
    l_interface_Table_name varchar2(2000);
    BEGIN
         SELECT interface_table_name
    into l_interface_Table_name
    FROM gl_interface_control
    WHERE interface_run_id = run_id;
         BEGIN     
    xxdb_gl_icaccntgdist_pkg.gl_int_jrnl_update (chr_errbuf,chr_retcode,l_interface_Table_name);
    RETURN(TRUE);
         END;
    END pre_module_hook;
    Make these changes in GL_IMPORT_HOOK_PKG.pre_module_hook function.
    You can make the changes through calling procedure using dynamic query under the function pre_module_hook.
    Thanks,
    Gaurav K
    Edited by: 972729 on Nov 22, 2012 4:46 AM

  • Custom Adapter - No content in Communication channel Monitoring for JCA

    HI,
         We have developed a Custom Adapter for our client in XI with name JCA and it is working absolutely fine.
         Issue: We are not getting any entries in Communication Channel Monitoring for success or Error Messages.
         We have used Audit log for success or Failure entries and they are coming fine in Messaging System but there coule be a standard way to get entries in Channel Monitoring.
        Our client needs the entries in CC monitoring instead of Customised Audit Logs.
        Please help.
    REgards,
    Anurag Garg

    HI Satish,
                     Thanks for answer. I am looking for this in Custom Adpater not in adapter module.
                     This log  creates a trace  File . Its not to do with getting messages in CC monitoring as we do get for File Adapter or other Adapters.
                   Like- Message Successfully put into the queue.
                         -  Successfully processed.
                     Such Messages are there in sample_ra. jar file code but they are not visible in CC Monitoring.
                   I think some extra code needs to be added to activate this in Monitoring.
                   Please suggest.
    REgards,
    Anurag Garg

  • Problem with Custom adapter

    Hi All,
    I am new to SUN Identity Management 7.1. I have developed a Custom Resource Adapter ,with this I am able to Create,Update,Disable,Enable a user in resource using tabbed form.But with Active Sync I am able to Create a user and not able to Update the user using active sync.
    The real update method is getting invoked using active sync but the attribute values like
    String genericID=user.getAttribute("genericID") etc are becoming null ie the values that are assigned are not passing to the real update method.
    Please suggest me to solve this issue.Your suggestions are important.
    Thanks,
    Madhu

    Hi All,
    No one is coming with suggestions,I think I need to explain my query in detail.
    I need to develop a custom adapter which should create,update,enable & disable a user in resource.
    I have developed the adapter ,through form I am able to create,update,enable & disable in to resource.Through ActiveSync also I am able to create a user into resource but I am not able to update the user.
    While creation of user, with active sync wizard I am placing values to extended attributes(columns names of a table in resouce).With those values the user is successfully created in to resource .
    While updation of user,with active sync wizard I am modifying extended attribute values to update the user.This time the realUpdate method in the adapter class is getting invoked but I am not able to retrieve the extended attributes in the method.I am getting null for those attributes.I am retrieving those values by
                String s2 = user.getAttribute("BRID");
                   System.out.println("brid : "+s2);
                String s3 = user.getAttribute("FunCode");
                   System.out.println("FunCode : "+s3);
              String s4=user.getAttribute("email");
                   System.out.println("email : "+s4);
                String s5 = user.getAttribute("MysqlSync Group");
                   System.out.println("MysqlSync Group : "+s5);I completed almost 75% of my task and I struck here for the last one week.
    Please give your valuable suggestions.
    Thanks in advance
    Madhu

  • MFL.convertToXml() gives 'Internal Error'  in custom adapter

    Has anyone seen the MFL.convertToXml() fail with:
    IllegalStateException: Internal Error, current node is null
    dies at com.bea.nonxml.readers.NonXMLReaderVisitor.nextToken(NonXMLReaderVisitor.java:110)
    Anyone got source to this?
    I call this method from within a custom adapter.
    I have an extremly simple MFL file as follows,
    Note that I added a 'IgnoreTheRest' at the en, to see if I could simplify it.
    <?xml version='1.0' encoding='US-ASCII'?>
    <!DOCTYPE MessageFormat SYSTEM 'mfl.dtd'>
    <MessageFormat name='MsgNoBits.h.2' version='2.02'>
    <!-- C declaration of message_id: unsigned short -->
    <FieldFormat name='message_id.2' type='UBigEndian2'/>
    <!-- C declaration of id: unsigned short -->
    <FieldFormat name='id.2' type='UBigEndian2'/>
    <!-- C declaration of num_bytes: unsigned long -->
    <FieldFormat name='num_bytes.2' type='UBigEndian4'/>
    <FieldFormat name='IgnoreTheRest' type='Filler' optional='y' length='1' repeat='*'>
    </FieldFormat>
    </MessageFormat>

    Not really...
    Just worked around it by doing the MFL.convertToXml() inside the ejb container.
    The way you get the binary data through the JCA to the container is by converting the binary data to a HexBinary XML type. (if you find another way please let me know)
    Pull out the binary once you receive it ( I use a JPD ). Then perform the translation. I think its very inefficient since you have to do bin-hex-bin-xml XML crap, but it works.
    heres the hexbinary snippet you use for your event definition.
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema targetNamespace="wlai/XXX_event"
    xmlns="wlai/XXXAppView_XXX_event"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:element name="XXXData"
    type="xsd:hexBinary"/>

  • Get Message details in custom adapter module

    Hello,
    Could you please let me know how can we retrieve following parameters in custom adapter module?
    Message size
    Message Mapping name
    Operation Mapping name
    Sender and Receiver Interface names
    Thanks!
    Regards,
    Shweta

    Hi Shweta
    Not all the information is available directly from the adapter module.
    Message size
    Retrieve the input stream of the payload, convert the stream to bytes and count the bytes length.
    Message msg = (Message) inputModuleData.getPrincipalData();
    XMLPayload payload = msg.getDocument();
    InputStream inStr = payload.getInputStream();
    // Convert inStream to bytes
    int size = bytes.length;
    Sender and Receiver interface names
    You can only get Sender interface in sender module, and receiver interface in receiver module. You can get the from the getAction() method.
    Message msg = (Message) inputModuleData.getPrincipalData();
    String interfaceName = msg.getAction().getName();
    Operation Mapping name
    This is not directly available from the Adapter Framework. One workaround is to access this via the Integration Directory API. With the Interface Determination Service API, you can read the Interface Determination object to get the associated mapping. To do this you have to make a SOAP call to the API.
    Message Mapping name
    I'm not sure how this can be retrieved as this is only available in ESR.
    If the module is on the receiver side, another option is to extract the information during mapping and store it into Dynamic Configuration, then in the receiver module, to extract it from Dynamic Configuration.
    Rgds
    Eng Swee

  • How to find proc/func name from package name and line number?

    Hi,
    We are using the pl/sql call stack dump (dbms_utility.format_call_stack) for some debugging purposes. But in the case of a package body execution, the dump does not return the name of the procedure/function that is being executed, but only the name of the package and the line number being executed. So, we have a requirement wherein we need to extract the type and name of a package subunit from the package name and line number.
    e.g.
    From the information package 'A', line number 739
    we should be able to deduce that line 739 is a part of *'function A.f'*
    Does the oracle database provide any native mechanism (PL/SQL packages or otherwise) to support such functionality? If it does not, how can we achieve the desired result?
    Thanks in advance,
    Shashank

    The approach we are currently planning to take up is this :
    1. Write PL/SQL code to parse the entire source (user_source) and build a database table with a structure like this :
    PACKAGE_NAME | UNIT_TYPE | UNIT_NAME | START_LINE | END_LINE
    =============================================
    A | PROCEDURE | P1 | 20 | 345
    A | FUNCTION | F1 | 347 | 629
    etc..
    2. Start PL/SQL package execution.
    3. Keep dumping call stack snapshots whenever a custom debug procedure is called.
    4. Dump the package name and line number to a log file.
    5. Using the package name and line number, query the table built in step 1 and build the final report which shows the control flow in a readable form.
    What we want is to get rid of step 5 and by some means get the logic to extract the unit type and name in step 4 itself.
    Keep them coming..
    Thanks and regards,
    Shashank

  • Wlsc problem with package name

    I am using wlsc ant task to generate my java code for a web service. Unlike the simplistic examples (HelloWorld and Complex) I have my complex types split into a separate .xsd file instead of putting them directly into the WSDL file.
    Is there a way to set the package name that will be generated for these types? It seems to generate everything into a java package based on the namespace (which is different than the wsdl).
    The wlsc ant task has an argument called "packageName" which I am setting. The java classes for the service itself use that package, just not the types defined in the xsd file(s). :(
    Thanks for any help

    see SAP documentation for package naming convention:
    Packages
    The following namespaces are available for packages:
    Package names beginning with a letter from A to S, or from U to X.
      Package names beginning with these letters are reserved for objects of the SAP standard system from the SAP namespace. You cannot create customer objects or objects from prefix namespaces in these packages.
    Note that the package name must be no more than 30 characters long. The name of the main package should reflect the content of the package Adjacent packages should have similar names.
    The Transport Organizer records changes to objects in these packages, so that they can be transported.
    These packages belong to the "SAP" transport layer and are assigned to an SAP software component (such as SAP_BASIS, SAP_APPL).
    Package names beginning with Y or Z
      You can create customer-specific objects from the customer namespace in these packages.
    The Transport Organizer records changes to objects in these packages, so that they can be transported, provided the SAP System has been set up appropriately. (For more information, see Setting the System Change Option). These packages are assigned to the software component HOME.
    So create the packages accordingly...

  • Import vs full package name

    So, I decided to fumble a bit with JavaFX. After having gotten myself a sh*tload of stress doing stuff in Flash and Actionscript, I'm ready for something that is intended as "code" from the ground up. One thing I ran into is this: AFAIK I have two identical custom nodes, the only difference is that one uses full package names and the other uses imports. The components just show an image.
    Full package version:
    public class SfeerNode extends javafx.scene.CustomNode
        public var sfeerimage : javafx.scene.image.Image;
        override function create() : javafx.scene.Node
            return javafx.scene.Group
                content:
                [     javafx.scene.image.ImageView
                          image: sfeerimage
    }And the import version:
    import javafx.scene.*;
    import javafx.scene.image.*;
    import javafx.scene.paint.*;
    import javafx.scene.shape.*;
    public class SfeerNode2 extends CustomNode
        public var sfeerimage : Image;
        override function create() : Node
            return Group
                content:
                [     ImageView
                          image: sfeerimage
    }Usage is very straight forward, just like ImageView, and I can toggle between the two by simply adding or removing "2" after "SfeerNode" in the main code.
    The problem: the full package version does NOT show the image, the import version does.
    Why?

    It is definitely a bug.
    It is possible to extend only CustomNode class to make the first sample work .
    import javafx.scene.CustomNode;
    public class A extends CustomNode {
        public var sfeerimage : javafx.scene.image.Image;
        override function create(): javafx.scene.Node{
            return javafx.scene.Group {
                content:[ javafx.scene.image.ImageView {
                          image: sfeerimage
    }

  • Package name in business content

    when i am trying to activate a cube in business content,when i click install and transport,i am getting a pop up window asking for a package name
    can somebody please give me some info on this,what is a package name,is it just like a folder or anything else

    You can go to se80 and open any Package and F1 over the name  of the package and you can see the sap Help...
    Package
    Packages extend the concept of development classes to improve modularization, encapsulation, and decoupling in the SAP System.
    Development classes, used until now, are simple containers for development objects, provided with a transport layer that specifies how they were to be transported. As an enhancement to development classes, packages include the following attributes: nesting, interfaces, visibility, and use accesses.
    Nesting is the ability of a package to include other packages within the package hierarchy.
    Visibility is an attribute of package elements. A development element can be visible from outside the package. (It is always visible inside its own package, though not necessarily all the packages embedded in this package). A development element is visible externally if it is included in at least one package interface.
    The use access gives a package the right to use the development elements in the package interface of another package. Note that this right is one-way only.
    Package
    Definition
    Related objects in the ABAP Workbench are grouped together in a package. The assignment of an object to a package is entered in the object directory (TADIR). The package determines the transport layer that defines the transport attributes of an object.
    The packages are entered in the table TDEVC. They can be maintained in the following transactions:
    Transaction SE80 -> Enter package -> Double-click the package
    Transaction SM30 - Table/view name V_TDEVC
    The packages are themselves objects of the ABAP Workbench. They belong to their own packages.
    In contrast to its predecessor, the development class, a package has the following additional characteristics:
    Packages can be nested.
    Packages can contain their 'visible development objects' (visible outside of the package) in package interfaces.
    Packages can have use access defined for other package interfaces.
    Use
    When an ABAP Workbench object is created, the system prompts you to assign it to a package. The package should describe the area that the object belongs to.
    The representation of the object tree in the ABAP Workbench (transaction SE80) uses the package as a navigation aid. If there are more than 100 objects of a certain type (that is, ABAP programs), the object tree can no longer be clearly represented and it becomes increasingly difficult to use the ABAP Workbench. In this case, we recommend creating new packages with the same transport layer and distributing the objects to the new packages on the basis of the areas they belong to.
    The following naming conventions for packages determine the packages' functions:
    Package begins with A-S or U-X:
    These packages are for SAP standard objects. Customer objects cannot be created in them. Changes to objects of these packages are recorded by the Transport Organizer (Request management) and can be transported (see field transport layer.
    Package begins with Y or Z:
    Customer objects can be created in these packages. Changes to objects in these packages are recorded by the Transport Organizer (Request management). The objects can be transported to other SAP Systems (see the field transport layer ).
    Package begins with T (private test package):
    When you create a package of this type, you can specify whether you want changes to be recorded. If so, objects that are edited are recorded in local requests by the Transport Organizer. This package does not belong to a transport layer. Objects can only be transported to other SAP Systems if a transport request is created.
    Package begins with $ (local package):
    Changes to objects are not recorded by the Transport Organizer. The package does not belong to a transport layer. The objects cannot be transported.
    Package begins with a namespace prefix:
    If you have reserved a namespace, then you can create packages (and other objects) whose names begin with the namespace prefix.
    (Example of a namespace prefix /COMPANY/, example of a corresponding package /COMPANY/DEVCLASS)
    Changes to these packages are recorded by the Transport Organizer, and can be transported.

Maybe you are looking for