JCo 3.00 migration

Hi all.
I´m used to use the JCo 2.x API, but now I´m developing for a portal version that seems to have this resource obsolete, so classes HCM_UTIL and ORGMANAGEMENTEVENTING are not installed in the system, so I need (Isn´t it??) to develop with JCo 3.00.
Problem is I have read the official SAP docs "SAPJCo_MigrationGuide_2.x_3.0_EN.pdf" and "SAPJCo_Doku_3.0_EN.pdf", but I have a lot of doubts that I´m not able to solve, like "Do I have to hardwrite my login info at the code??" For me this is no possible. "Can I use the SAP Connection Wizard of the Eclipse??"... And a few more.
Does anyone knows about a "howto" or a place with documentation or examples about this for me to learn it?? Can anyone give me a few examples or something like that??
Thanks a lot in advance.

I just need a "portalapp.xml" and a "main.java" to find out the info myself...
Just an example for a poor developer, please

Similar Messages

  • Random JCO Communication Failure Error after Hardware Migration

    Greetings experts,
    we had a migrated our XI server to new hardware and had couple of SLD related issues which were solved by the migration team. However, we are getting JCO communication failure very frequent whenever we use JCO from JAVA to call an RFC. The weird thing, if you restarted the message it will be successful.
    The error message in the message monitor :
    "COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection"
    Any idea to solve this random issue?

    Hi again,
    the number of connection was increased to 200 but with no effects. Also, the user used to connect is a system user which does not need a ticket.
    This is my connection code
                   mConnection = JCO.createClient("600", // Client
              "USER", // Username
              "PASSWORD", // Password
              "EN", // Language
              "hostname", // Host
              "01"); // System Number
    do I need to add anything else if I am using a clustered system?

  • SLD/JCo Migration to new host

    Dear Experts,
    I have gone through many posts but still not able to understand fully the procedure to migrate SLD from one host to another. So its my humble request you to read my issue and guide me.
    We have a situation that we have moved from physical to virtual host on our SLD. But when I shutdown the previous host, my ESS/MSS on Portal stops functioning.
    My Landscape is : Portal 7.1  - Old SLD -- Was serving as both Solution Manager and SLD (for around 20-30 systems)
    Now we want to move the OLD SLD to a new host, -- New SLD -- Will serve as SLD for all systems.
    There is one production Portal system which has ESS/MSS with Jco's, it is currently pointing to OLD SLD. When I login to OLD SLD and search for my Production Portal, I can see that it has few Jco Destinations and few "deployed objects" as shown in screenshot below
    These are the steps I have followed in my new SLD.
    1. Went to Visual Admin of my Portal system -- Changed SLD Data Supplier (CIM) to NEW SLD. Restarted Portal
    2. Logged in to new SLD and created JCO Destinations (exactly same as in OLD SLD)
    This is my NEW SLD, I cant see the "deployed objects" but i have created the JCO destinations (manually)
    But then, I am getting errors in ESS/MSS Applications for Jco related.
    Can someone please help me in figuring out what I am missing ??
    1.     Importing CIM data in new SLD from old SLD ??
    Any guidance on this will be helpful.
    Thanks,

    Hi Rajat,
    Take a look at More on System Landscape Directory. There are several blogs there that talk about migrating from one SLD to another. (Especially Switching between 2 SLD Systems in Sync with an LMDB or a 3rd SLD).
    It sounds to me like you changed the setup for the data supplier side, (so your new SLD has the correct data) but you haven't changed the SLD-client setup of the portal (so your portal doesn't know to look at the new SLD for data). Take a look at this SAP help document, Synchronizing the System Landscape Directory with the Portal, and see if you can find what you need there.
    I hope this helps!
    Best regards,
      --Tom

  • JCo definitions lost during OS/DB migration of single stack Java

    Hello All,
    I am migrating a single stack Java system release 7.0 from SolarisOracle to AIXOracle. The application running on this system happen to be GRC components. The whole migration includes SLD system migration as well. The issue is that after the system copy, definition of all JCo destinations is gone. The only thing that is left from JCo destinations is the name. I can create these JCo destinations after the copy but that is manual work and will extend the migration window.
    Has anyone seen this issue?
    Is there anyway to copy JCo destinations from one Java stack to another?
    Thanks,
    Farshid

    Hello Mark,
    thanks for the SAP Note.
    Seems within the 6 years since 2005 there were no NW Systemcopies with a really big number of JCO Connections inside...
    resulting into that SAP was not forced to do something in this area.
    I'm curious if the JCO interface of 7.3 was reworked in that area as well...
    -Ulf

  • Migration of SAP jco 2.1.10 - 3.0

    Hey ,
    I am trying to upgrade a middleware component developed in jco 2.1.10 to jco 3.0 .All I have done that is I have replaced the sapjco 3.0 jar files in eclipse and there seems to be typical syntax problems after this , out of which I am unable to resolve some of the syntaxes also these are not provided in the documentation guide (Obtained from SAP market place).
    1) JCO.releaseClient(..) //how to replace this in SAP jco 3.0 cant find anything resemblance
    2) JCO.addClientClientPool(pool_name , pool_size , properties); //how to replace this in SAP jco 3.0 cant find anything resemblance
    3) Further in the documentation it has been said to replace JCO.Client (jco 2.1.10) -> JCoClient (jco 3.0) , but it is showing "JCoClient cannot be resolved to a type" , same with JCO.Server
    Can anyone plz help regarding these syntaxes.
    Thanks in advance

    > 1) JCO.releaseClient(..) //how to replace this in SAP jco 3.0 cant find anything resemblance
    > 2) JCO.addClientClientPool(pool_name , pool_size , properties); //how to replace this in SAP jco 3.0 cant find anything resemblance
    Please read Adapting Connection Management (p.7) in document (see example code).
    > 3) Further in the documentation it has been said to replace JCO.Client (jco 2.1.10) -> JCoClient (jco 3.0) , but it is showing "JCoClient cannot be resolved to a type" , same with JCO.Server
    Can you provide link to document where you found this statement?

  • Failed to create deployable object '********' since it is not a Web Dynpro object - Migration from 7.0 to 7.4

    I have installed NWDS 7.30 EHP1 SP 14 PAT000   with JVM 6 SAP AG
    to   migrate wedynpro development components from 7.0 to
    NW7.4 WAS SAP AG 1.6.0_85 on Windows Server 2008 R2 6.1  SP09 PAT000
    In track imported below SCAs of version  7.31 SP14 .
    Could able to migrate and build in NWDS, getting deployment errors.
    Followed   
    http://scn.sap.com/docs/DOC-55584 
    and   
    http://scn.sap.com/community/nwdi/blog/2014/03/26/nwdi-vs-nwdi-content 
    COMP_BUILDT
    ECM-CORE
    ENGFACADE
    ENGINEAPI
    ESCONF_BUILDT
    FRAMEWORK
    MOIN_BUILDT
    SAP_BUILDT
    WD-RUNTIME
    Deployment Errors:-
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] 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.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
        at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
        at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] 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.3297] Operation [update] of [sdu id: [XXXXXXX.com_home~chgemail]
    sdu file path: [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ] failed
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:100)
        at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)
        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 [update] of [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear] failed
        at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:489)
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)
        ... 11 more
    Caused by: com.sap.engine.services.servlets_jsp.webcontainer_api.exceptions.WebContainerExtensionDeploymentException: Error during deployment of application {0}
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:52)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeployInternal(ExtensionHandler.java:169)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeploy(ExtensionHandler.java:129)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerProvider.deploy(WebContainerProvider.java:334)
        at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:360)
        at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:327)
        at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:446)
        at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:409)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:478)
        at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:234)
        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.update(DeployServiceImpl.java:582)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:487)
        ... 12 more
    Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.DeploymentException: Failed to deploy application 'XXXXXXX.com/home~chgemail'.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:324)
        at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.notifyOnDeploy(DeployableObjectInternal.java:122)
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:49)
        ... 27 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:79)
        at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObjectFactory$1.getDeployableObject(AbstractDeployableObjectFactory.java:87)
        at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObject(WDDeployableObject.java:43)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.calculateVMOsOfDeployableObject(RepositoryContainerHook.java:264)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:181)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:297)
        ... 29 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.
        at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:228)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:77)
        ... 34 more
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]

    C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear
    can you find this ear in your local drive?

  • Cfhttp: Migration of Webservice from CF 6.1 to CF 8.0.1 fails

    Hello,
    our application is consumer of a webservice. It works well on CF 6.1 (Sun Solaris) for longer time.
    Now we have to migrate to a new platform with CF 8.0.1 on Linux. The service returns "Connection Failure".
    Because of security reasons username and password must be in the SOAP header. So we implemented the service invocation via CFHTTP.
    Can please anybody help?
    We assume that the error has something to do with a wrong or wrong interpreted content length of the returned code.
    Thank you very much in advance and greetings from Germany.
    Rainer
    Facts:
    - The physical connection to the webservice server is ok. Requests of us can be found in the logfiles there. It seems they are processed there normally.
    - If we send wrong XML data intentionally (invalid XML-syntax, wrong user name...) the returned data contains sensible error messages which comes definitly from the target server.
    - If we send correct XML data the only file content which is return is "Connection Failure"
    - There are no hints in the logfiles.
    - The sended data does not contain any special character.
    - The returned data can contain special characters (e.g. German umlauts).
    The code:
    <cfprocessingdirective pageencoding="iso-8859-1">
    <!--- ... --->
    <cfsavecontent variable="soap"><?xml version="1.0" encoding="utf-8" ?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:opal="#request.opal_webservice_ns#">
       <soapenv:Header>
          <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext" soapenv:mustUnderstand="1">
           <wsse:UsernameToken>
            <wsse:Username>#request.opal_username#</wsse:Username>
            <wsse:Password Type="wsse:PasswordText">#request.opal_password#</wsse:Password>
           </wsse:UsernameToken>
         </wsse:Security>
       </soapenv:Header>
       <soapenv:Body>
          <opal:OPAL_spc-_spcGet_spcAREMIS_spcOpportunity_spcData_GetAREMISData_Input>
             <opal:Process_spcInstance_spcId></opal:Process_spcInstance_spcId>
             <opal:Object_spcId>#ucase(opalid)#</opal:Object_spcId>
             <opal:Siebel_spcOperation_spcObject_spcId>?</opal:Siebel_spcOperation_spcObject_spcId>
             <opal:Error_spcCode></opal:Error_spcCode>
             <opal:Error_spcMessage></opal:Error_spcMessage>
          </opal:OPAL_spc-_spcGet_spcAREMIS_spcOpportunity_spcData_GetAREMISData_Input>
       </soapenv:Body>
    </soapenv:Envelope>
    </cfsavecontent>
    <cfhttp method="post" url="#request.opal_webservice_url#" throwonerror="no" timeout="20" charset="utf-8">
        <cfhttpparam type="Header" name="charset" value="UTF-8" />
        <cfhttpparam type="header" name="SOAPAction" value="#request.opal_webservice_soapaction#">
        <cfhttpparam type="header" name="Host" value="#request.opal_webservice_host#">
        <cfhttpparam type="header" name="Content-Length" value="#len(soap)#">
        <cfhttpparam type="XML" name="XML" value="#soap#">
    </cfhttp>
    <cfdump var="#cfhttp#" label="cfhttp">
    Technical data of the new server (which fails):
    Operating system (uname -a):
    Linux mhpa3y4c 2.6.18-028stab060.8 #1 SMP Mon Feb 9 20:25:36 MSK 2009 i686 i686 i386 GNU/Linux
    Server Details 
    Server Product  ColdFusion 
    Version  8,0,1,195765   
    Edition  Enterprise   
    Serial Number  1185-5039-8342-3354-3033-xxxx   
    Operating System  UNIX   
    OS Version  2.6.18-028stab060.8   
    Update Level  /opt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/updates/hf801-1878 .jar   
    JVM Details 
    Java Version  1.6.0_14   
    Java Vendor  Sun Microsystems Inc.   
    Java Vendor URL  http://java.sun.com/ 
    Java Home  /usr/java/jdk1.6.0_14/jre   
    Java File Encoding  ASCII   
    Java Default Locale  en_US   
    File Separator  /   
    Path Separator  :   
    Line Separator  Chr(10) 
    User Name  webrun   
    User Home  /home/webrun   
    User Dir  /opt/jrun4/bin   
    Java VM Specification Version  1.0   
    Java VM Specification Vendor  Sun Microsystems Inc.   
    Java VM Specification Name  Java Virtual Machine Specification   
    Java VM Version  14.0-b16   
    Java VM Vendor  Sun Microsystems Inc.   
    Java VM Name  Java HotSpot(TM) Server VM   
    Java Specification Version  1.6   
    Java Specification Vendor  Sun Microsystems Inc.   
    Java Specification Name  Java Platform API Specification   
    Java Class Version  50.0   
    Java Class Path  CF Classpath
    pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/updates/hf801-1878.ja r:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/updates/chf8010002.ja r:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/mlibwrapper_jai.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jaxb-api.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-net-1.4.0.jar :  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jpedal.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/xml-apis.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/verity.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jai_core.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/asn1.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/xercesImpl.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/certj.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/smpp.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jnbcore.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/vparametric.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/wsdl2java.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/wsdl4j-1.5.1.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/derbytools.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/axis.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-beanutils-1.6 .jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/bcel.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jstack.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/java2wsdl.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jintegra.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cf-assembler.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/im.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/poi-2.5.1-final-20040 804.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/saaj.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/xsdlib.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ldap.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/clibwrapper_jiio.jar:   pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jutf7-0.9.0.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/mysql-connector-java- commercial-5.0.5-bin.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/flex-messaging.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/iTextAsian.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/derbyclient.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-discovery-0.2 .jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/smack.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/mm-mysql-jdbc.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/vsearch.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cfusion.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/postgresql-8.1-407.jd bc3.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ib6core.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/tools.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ib6swing.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cfusion-req.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/flashgateway.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-digester-1.7. jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ldapbp.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/mail.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/log4j-1.2.12.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/STComm.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jaxb-libs.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jsch-0.1.28m.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/vadmin.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cf4was.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cf-logging.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/crystal.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jai_imageio.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/xalan.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/pdfencryption.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/derbyrun.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cf-acrobat.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jax-qname.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/derby.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ri_generic.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/httpclient.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/izmado.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ant.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/derbynet.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/namespace.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/backport-util-concurr ent.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/iText.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-httpclient-3. 0.1.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-collections-2 .1.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/macromedia_drivers.ja r:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jaxb-xjc.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jakarta-oro-2.0.6.jar :  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cdo.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ib6addonpatch.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-logging-api.1 .0.4.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jaxrpc.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ant-launcher.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cf4was_ae.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ib6util.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/webchartsJava2D.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/cdohost.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jai_codec.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/metadata-extractor-2. 2.2.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jakarta-slide-webdavl ib-2.1.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/FCSj.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/relaxngDatatype.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jdom-1.0.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jaxb-impl.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/flex-messaging-opt.ja r:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/poi-contrib-2.5.1-fin al-20040804.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/flex-messaging-common .jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/wc50.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/flex-messaging-req.ja r:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/jeb.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-logging.1.0.4 .jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/rome-cf.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/commons-codec-1.3.jar :  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/ib6http.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/tt-bytecode.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/lib/:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/gateway/lib/examples.jar:   pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/gateway/lib/:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/flex.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/jcert.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/batik-css.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/batik-util.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/commons-logging.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/batik-transcoder.jar:   pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/oscache.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/jsse.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/jakarta-oro-2.0.7.jar :  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/commons-discovery.jar :  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/batik-awt-util.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/concurrent.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/jnet.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/batik-ext.jar:  pt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfform/jars/:  :
    Server Classpath
    /opt/jrun4/servers/lib:
    /opt/jrun4/servers/lib/jrun-patch.jar:
    /opt/jrun4/servers/lib/pbclient42RE.jar:
    /opt/jrun4/servers/lib/pbserver42RE.jar:
    /opt/jrun4/servers/lib/pointbase-service.jar:
    /opt/jrun4/servers/lib:
    /opt/jrun4/servers/lib/jrun-patch.jar:
    /opt/jrun4/servers/lib/pbclient42RE.jar:
    /opt/jrun4/servers/lib/pbserver42RE.jar:
    /opt/jrun4/servers/lib/pointbase-service.jar:
    /opt/jrun4/lib:
    /opt/jrun4/lib/instutil.jar:
    /opt/jrun4/lib/java2wsdl.jar:
    /opt/jrun4/lib/jrun-ant-tasks.jar:
    /opt/jrun4/lib/jrun-xdoclet.jar:
    /opt/jrun4/lib/jrun.jar:
    /opt/jrun4/lib/jrunwizard-installer.jar:
    /opt/jrun4/lib/jrunwizard.jar:
    /opt/jrun4/lib/jspc.jar:
    /opt/jrun4/lib/macromedia_drivers.jar:
    /opt/jrun4/lib/migrate.jar:
    /opt/jrun4/lib/mysql-connector-java-commercial-5.0.5-bin.jar:
    /opt/jrun4/lib/oem-xdoclet.jar:
    /opt/jrun4/lib/sniffer.jar:
    /opt/jrun4/lib/webservices.jar:
    /opt/jrun4/lib/wsconfig.jar:
    /opt/jrun4/lib/wsdl2java.jar:
    /opt/jrun4/lib/xmlscript.jar:
    /opt/jrun4/lib/jrun.jar
    Java Ext Dirs  /usr/java/jdk1.6.0_14/jre/lib/ext:/usr/java/packages/lib/ext
    Technical data former server (which runs well):
    Operating System (uname -a):
    SunOS MHPA24ZC 5.8 Generic_117350-45 sun4us sparc FJSV,GPUZC-M
    Server Details 
      Server Product 
       ColdFusion MX
      Version 
       6,1,0,hf52806_61
      Edition 
       Enterprise
      Serial Number 
       CED600-55949-37264-xxxxxx
      Operating System   
       UNIX
      OS Version 
       5.8
      JVM Details 
      Java Version 
       1.4.2
      Java Vendor 
       Sun Microsystems Inc.
      Java Vendor URL 
       http://java.sun.com/
      Java Home 
       /export/home/coldf/coldfusionmx/runtime/jre
      File Separator 
      Path Separator 
      Line Separator 
       Chr(10)
      User Name 
       coldf
      User Home 
       /export/home/coldf
      User Dir 
       /export/home/coldf/coldfusionmx/runtime/bin
      Java VM Specification Version 
       1.0
      Java VM Specification Vendor 
       Sun Microsystems Inc.
      Java VM Specification Name 
       Java Virtual Machine Specification
      Java VM Version 
       1.4.2-b28
      Java VM Vendor 
       Sun Microsystems Inc.
      Java VM Name 
       Java HotSpot(TM) Server VM
      Java Specification Version 
       1.4
      Java Specification Vendor 
       Sun Microsystems Inc.
      Java Specification Name 
       Java Platform API Specification
      Java Class Version 
       48.0
      Java Class Path 
       /export/home/coldf/coldfusionmx/runtime/servers/lib:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf52806_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf53398_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf53419_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf53486_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf53685_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf53797_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf53813_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf53852_61.jar:  /export/home/coldf/coldfusionmx/runtime/servers/lib/hf54464_61.jar:  /export/home/coldf/coldfusionmx/servers/lib:  /export/home/coldf/coldfusionmx/lib/cfusion.jar:  /export/home/coldf/coldfusionmx/lib:  /export/home/coldf/coldfusionmx/lib/NetComponents.jar:  /export/home/coldf/coldfusionmx/lib/bcel.jar:  /export/home/coldf/coldfusionmx/lib/cf4was.jar:  /export/home/coldf/coldfusionmx/lib/cf4was_ae.jar:  /export/home/coldf/coldfusionmx/lib/cfmx-ssl.jar:  /export/home/coldf/coldfusionmx/lib/cfmx_bootstrap.jar:  /export/home/coldf/coldfusionmx/lib/cfusion.jar:  /export/home/coldf/coldfusionmx/lib/cfx.jar:  /export/home/coldf/coldfusionmx/lib/collections.jar:  /export/home/coldf/coldfusionmx/lib/crimson.jar:  /export/home/coldf/coldfusionmx/lib/flashgateway.jar:  /export/home/coldf/coldfusionmx/lib/httpclient.jar:  /export/home/coldf/coldfusionmx/lib/izmado.jar:  /export/home/coldf/coldfusionmx/lib/jakarta-oro-2.0.6.jar:  /export/home/coldf/coldfusionmx/lib/java2wsdl.jar:  /export/home/coldf/coldfusionmx/lib/jaxp-api.jar:  /export/home/coldf/coldfusionmx/lib/jdom.jar:  /export/home/coldf/coldfusionmx/lib/ldap.jar:  /export/home/coldf/coldfusionmx/lib/ldapbp.jar:  /export/home/coldf/coldfusionmx/lib/log4j.jar:  /export/home/coldf/coldfusionmx/lib/macromedia_drivers.jar:  /export/home/coldf/coldfusionmx/lib/mail.jar:  /export/home/coldf/coldfusionmx/lib/pbclient42RE.jar:  /export/home/coldf/coldfusionmx/lib/pbembedded42RE.jar:  /export/home/coldf/coldfusionmx/lib/pbserver42RE.jar:  /export/home/coldf/coldfusionmx/lib/pbtools42RE.jar:  /export/home/coldf/coldfusionmx/lib/tools.jar:  /export/home/coldf/coldfusionmx/lib/tt-bytecode.jar:  /export/home/coldf/coldfusionmx/lib/webcharts.jar:  /export/home/coldf/coldfusionmx/lib/webchartsJava2D.jar:  /export/home/coldf/coldfusionmx/lib/webservices.jar:  /export/home/coldf/coldfusionmx/lib/wsdl2java.jar:  /export/home/coldf/coldfusionmx/lib/xalan.jar:  /export/home/coldf/coldfusionmx/runtime/lib/jrun.jar:  /export/home/coldf/coldfusionmx/runtime/lib:  /export/home/coldf/coldfusionmx/runtime/lib/instutil.jar:  /export/home/coldf/coldfusionmx/runtime/lib/java2wsdl.jar:  /export/home/coldf/coldfusionmx/runtime/lib/jrun-ant-tasks.jar:  /export/home/coldf/coldfusionmx/runtime/lib/jrun-xdoclet.jar:  /export/home/coldf/coldfusionmx/runtime/lib/jrun.jar:  /export/home/coldf/coldfusionmx/runtime/lib/jspc.jar:  /export/home/coldf/coldfusionmx/runtime/lib/migrate.jar:  /export/home/coldf/coldfusionmx/runtime/lib/oem-xdoclet.jar:  /export/home/coldf/coldfusionmx/runtime/lib/sniffer.jar:  /export/home/coldf/coldfusionmx/runtime/lib/webservices.jar:  /export/home/coldf/coldfusionmx/runtime/lib/wsconfig.jar:  /export/home/coldf/coldfusionmx/runtime/lib/wsdl2java.jar:  /export/home/coldf/coldfusionmx/runtime/lib/xmlscript.jar:  /oracle/orav920/jdbc/lib/classes12.jar:  /home5/coldf/java:  /home5/coldf/java/csvjdbc.jar:  /home5/coldf/java/verona:  /home5/coldf/java/verona/jCO.jar:  /home5/coldf/java/csvjdbc.jar:  /export/home/coldf/coldfusionmx/lib/cfusion.jar
      Java Ext Dirs 
       /export/home/coldf/coldfusionmx/runtime/jre/lib/ext

    And you can use the ColdFusion Code Analyzer
    http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec0d04c -7fee.html
    But  yeah, as Dan said, definitely set up a test server and plan a series of tests that must pass.
    -Fernis

  • Java JCo SAP XI RFC SAP R/3 6.C ... Unicode issue

    Hello,
    My scenario is very simple. I'd like to connect a Java program to a SAP R/3 (MDMP) for RFC calls (in both direction), using SAP XI (some of the RFC calls will redirected to some other systems). I use SAP JCo v2.1.8 and tried with Java 1.4.2_09 and Java 6.0.
    It works well when the Java program is calling a function module, but when SAP R/3 is doing it, the returned texts looks like: S#A#P# #J#C#o# #v#2#.#1#.#8# #(#2#0#0#6#-#1#2#-#1#1#)# (the text should be SAP JCo v2.1.8).
    It looks like an issue with Unicode. Although I didn't check the Unicode checkbox in the RFC sender adapter (the RFC receiver one doesn't offer the possibility to specify unicode or not).
    Do anyone have a solution ? Is it a code in the Java program or something to set in SAP XI / SAP R/3 ?
    Thanks in advance for your help.

    This is a workaround solution. In the case of this prototype it is ok, but the final plan is to migrate a web based application. It was directly connected to one SAP R/3, but now we would like to connect it to SAP XI because a few RFC calls will be re-directed to some other systems, but the majority of them will we'll still be sent to the SAP R/3. We don't want to make development on this part for cost reason (and time). Plus on some text there are the "#" character that is legitimate.

  • PI 7.0 DB migration

    Hi
    We are using PI 7.0 (Windows environment).This is HA/Distributed environment
    PI Application and DB both are running on different host with Microsft Cluster technology for HA
    We wanted to move DB instance (only DB as we do not want to make any change into Application) on Linux or Solaris Server
    Do we just need to use statndard OS/DB Migration system copy Guide for DB instance move to another server? We also want to have HA for DB after moving to new server
    In addition to DB migration do we need to make any changes for below configuration after DB move to new server?
    1. Change in PI Exchange profile file
    2. SLD Configuration Changes
    3. JCO Connection configuration Change
    4. Visual and Configtool related changes
    I appreciate expert opinion on this
    Thanks in advance
    Thanks
    Deelip

    Hi Deelip,
    You need to use standard OS/DB migration, though in this case you are just migrating your DB and not application, but it is advisable to run sapinst on both servers because I am assuming that generally hostname naming convention for Windows and Unix/Linux changes plus your listener settings on application server will also change,
    ....but if you do not wish to run migration sapinst on your app server then you need to do manual changes on app. server for listener and your DB hostname should not change.
    Then you need to check "R3trans -d" for ABAP part and you need to check Configtool is getting connected or not.
    Let say you will be successful in making your java up in that case also you need to send your new data to SLD, check your SMSY, LMDB for correctness of DB server information.
    When your java will be up, then VA and JCo should not be an issue.
    Unless you don't have enough time to go through this experimental process. Please run migration on both servers and follow PI db copy documents also for few missing post steps.

  • "jco.server.unicode" is gone in JCO 3.0.5??!!

    Recently  we have migrated from   JCO 2.1.8  to  3.0.5.   Currently we are witnessing some problems with communications from non-Unicode Sap systems.
    In the previous version  (JCO 2.1.8)  JCoIDoc.Server had a property "jco.server.unicode"  in the latter one the property  is gone.
    AS far as I  understand, JCo3 Server based on the data sent form a client recognizes encoding and applies proper conversion. However when we try to establish a non-Unicode connection ( from a Unicode enabled system),  through setting In the SM59 transaction (tab MDMP & Unicode) u201ECommunication Type with Target Systemu201D  to Non-Unicode, we are getting  the following error :
    com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????
    ????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
            at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
            at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
            at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
            at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
            at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
            at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
            at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
            at java.lang.Thread.run(Thread.java:619)
    11:15:20,062 ERROR   Sap server details
    Class: com.syncron.bpe.engine.extinterface.sap.idoc.SapIDocServer
    Program id: GIM
    Thread name: JCoServerThread-1
    Registered (at gateway) connection count: 5
    Max thread count: 1
    Exception occured
    com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: IDocException occurred (raised by system karbie-nc6400|a_rfc)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2395)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
            at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
            at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
            at java.lang.Thread.run(Thread.java:619)
    Caused by: RfcException: karbie-nc6400
        message: IDocException occurred
        Return code: RFC_FAILURE(1)
        error group: 104
        key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by karbie-nc6400|a_rfc
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2785)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
            ... 4 more
    Caused by: RfcException: karbie-nc6400
        message: IDocException occurred
        Return code: RFC_FAILURE(1)
        error group: 104
        key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by karbie-nc6400|a_rfc
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3329)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
            ... 7 more
    Caused by: com.sap.conn.idoc.IDocRuntimeException: IDocException occurred
            at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:151)
            at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
            at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
            ... 8 more
    Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "???????
    ???????????????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
            at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
            at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
            at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
            at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
            at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
            ... 10 more
    With JCO 2.1.8  we used to solve it through setting the mentioned "jco.server.unicode"   to 1, in the  current one it seems that there is not much to configure regarding encoding.
    Please advice.

    In unicode ABAP backend systems you always have to set the destination in SM59 to "Unicode" if the communication partner is JCo. There is no choice for setting the Non-Unicode option. It won't work.
    JCo3 does not require a manual setting of the "jco.server.unicode" property any longer. Therefore the property has been deleted. In JCo3 you don't have to take care for this anymore.

  • JCo - Unicode issue

    Hi,
      Recently, we migrated SAP to unicode version. Due to this, we are getting the below error when we try to connect from SapJCo to SAP. The version of JCo used is 2.1.6. SAP is hosted on Unix and Java applications are hosted on Windows. We tried with jco.client.codepage= 4103; we are getting different error(RFC_ERROR_LOGON_FAILURE: >> unknown RFC error, no error log found <<) when we give the codepage property.
    Please let us know how to resolve the below issue:
    Exception in thread "main" com.sap.aii.proxy.framework.core.BaseProxyException: Conversion error between two character sets., error key: RFC_ERROR_SYSTEM_FAILURE
          at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
    At the SAP side, we are getting the below errors
    Error analysis
    The error probably occurred when installing the
    R/3 system.
    The termination was triggered in function "RfcExtendedReceive"
    of the SAP kernel, in line 301 of the module
    "//bas/700_REL/src/krn/rfc/abrfcrcv.c#5".
    The internal operation just processed is "FUNC".
    Internal mode was started at 20101124144800.
      CLUDE INCL_INSTALLATION_ERROR
    Edited by: manohar mirle on Nov 26, 2010 2:03 PM

    This got resolved.
    We had to make changes to the XML which is embedded in the java code of R3Connector classes. Changed the encoding type and data types in the XML. It went through.

  • Migrating SAP NetWeaver WebDynpro 7.0 Applications to WebDynpro 7.3/7.4

    Hi,
    We are trying to migrate applications from SAP NetWeaver Portal 7.0 to 7.4. The applications were created using SAP NetWeaver WebDynpro Java 7.0 and we're trying to import the Development Components (DC) using SAP NetWeaver Development Studio CE 7.3. However we're encountering an error after rebuilding and repairing the applications
    Error Details:
    Generation of component ****Comp is terminated with an exception (com.sap.ide.mmservices.wd.general.NoWebDynproContentException: No Web Dynpro content found for project "***". If this project is a Development Component, check if "SapMetamodelWebdynproContent.zip" is present in the classpath.)      [Error: com.sap.ide.webdynpro.generation.eclipse.GenerationEclipse  Thread[Worker-29,5,main]]
    The project was not built since its  built path is incomplete. Cannot find the class for com.sap.mw.jco.JCO$Client.
    The type com.sap.mw.jco.JCO$Client cannot be resolved. It is indirectly referenced from required .class files
    Any ideas regarding the errors?
    thank you.

    Hi,
    thank you all for your replies.
    there are no longer errors anymore before deployment. However, once we deploy we encounter a build error.
    here are the details:
    !ENTRY org.eclipse.ui 4 4 2014-06-18 11:13:00.188
    !MESSAGE java.lang.NullPointerException
    !STACK 0
    java.lang.NullPointerException
      at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
      at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
      at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
      at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
      at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorationResult(LightweightDecoratorManager.java:378)
      at com.sap.ide.tools.core.viewerfwk.ui.tree.wrapper.ProjectWrapper.getTreeNodeLabelText(ProjectWrapper.java:74)
      at com.sap.ide.webdynpro.wdexplorer.tree.WDViewLabelProvider.getText(WDViewLabelProvider.java:98)
      at com.sap.ide.tools.core.viewerfwk.ui.tree.CompoundLabelProvider.getText(CompoundLabelProvider.java:81)
      at org.eclipse.jface.viewers.ViewerComparator.compare(ViewerComparator.java:135)
      at com.sap.ide.tools.core.viewerfwk.ui.tree.CompoundViewerSorter.compare(CompoundViewerSorter.java:77)
      at org.eclipse.jface.viewers.ViewerComparator$1.compare(ViewerComparator.java:187)
      at java.util.Arrays.mergeSort(Arrays.java:1270)
      at java.util.Arrays.mergeSort(Arrays.java:1281)
      at java.util.Arrays.sort(Arrays.java:1210)
      at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:185)
      at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:625)
      at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2578)
      at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1863)
      at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:716)
      at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1838)
      at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1794)
      at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1780)
      at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1457)
      at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1392)
      at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:402)
      at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1353)
      at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1455)
      at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537)
      at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1414)
      at com.sap.ide.dictionary.ddicexplorer.tree.DDICContentProvider$1.run(DDICContentProvider.java:709)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
      at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
    Do you have any ideas?
    thank you very much!

  • Query on JCO Version

    Hi,
    We are currently migrating from SAP J2EE Engine 6.20 to SAP J2EE Engine 7.0. From the support note 549268 we understand that the SAP J2EE Engine 7.00 has a SAP JCo version 6.45. But what we need to understand is that what is the equivalent stand-alone version of JCo for SAP JCo 6.45. We use the stand-alone version of JCo during the application development and hence we would need the equivalent stand-alone for SAP JCo 6.45.
    Thanks
    JLN

    Hi,
    Check this [link|Can SAP JCo 2.x co-exist with the integrated SAP JCo 6.45 in NW 7.0?;
    Thanks
    Sunny

  • How to create an instance of JCO.Table

    hi,
    I am facing a problem while migrating from JCO Client service to Connector Framework.
    Basically i get the output in the format of IRcordSet after calling Back End system.
    I need to convert this to JCO.Table to continue in my code so that i wont change all the code which uses JCO.Table.
    Ex:
                   IConnection connection = null;
                   IConnectorGatewayService service = (IConnectorGatewayService) PortalRuntime.getRuntimeResources().getService(IConnectorGatewayService.KEY);
                   try {
                             ConnectionProperties props = new ConnectionProperties(request.getLocale(),request.getUser());
                             String destination = Util.getBESystemID(request);
                             connection = service.getConnection(destination, props);
                             IInteraction interaction = connection.createInteractionEx();
                             IInteractionSpec intSpec = interaction.getInteractionSpec();
                             intSpec.setPropertyValue("NAME", BE_FM_DOWNLOAD); //Function Call /RPM/MSPC_DOWNLOAD;
                             RecordFactory rf = interaction.getRecordFactory();                    
                             MappedRecord inputParams = rf.createMappedRecord("INPUT");
                             //inputParams.put(BE_IN_DOWNLOAD_APP, BE_IN_DOWNLOAD_APP_DEFVALUE, JCO.TYPE_STRING);
    JCO.Table to Object (??)
                             inputParams.put(BE_IN_DOWNLOAD_EXPORTLOG, exportLog);
    exportlog is type JCO.Table
                             MappedRecord outputParams = (MappedRecord) interaction.execute(intSpec, inputParams);
                             connection.close();
              Object result = outputParams.get(BE_OUT_DOWNLOAD_EXPORTLOG);
              //JCO.Table m_downloadExportLog = (JCO.Table)result;//error this wont work
    //Here i need to get m_downloadExportLog
    IRecordSet irs = (IRecordSet)Object;
    Here how can get JCO.Table from IRecordSet???
    Thanks in advance!!
    Regards,
    Ramesh.

    You could retrieve the values and store in a TableView in the following manner.....
    //zData is a JCo.Table
         for (int i = 0; i < TableData.getNumRows(); i++) {
                             //ABCBean zAIPBean = (ABCBean)zData.getRow(i);
                   j = 0;
              //for (JCO.FieldIterator e = zData.fields(); e.hasMoreElements(); ){
                   JCO.FieldIterator e = zData.fields();
                   while (e.hasMoreElements()) {
                             JCO.Field field = e.nextField();
                             data<i>[j] = field.getString();
                             j = j + 1;
                        zData.nextRow();
    Consider rewarding points if the issue is solved ...
    Thanks,
    Devina

  • Missing method fromXML() in JCO 3.0.5

    Hi,
    I'm currently upgrading our company's SAP connector code from JCO 2.1.8 to JCO 3.0.5. There is a lot of refactoring necessary of course, but so far I've always found in the new 3.0 API what I needed.
    But now I'm stuck. In JCO 2.1.8 there was a method fromXML() in class JCO.Record, which I used frequently. Where is this functionality in JCO 3.0? The new class JCoRecord still has the method toXML(), but no fromXML() anymore!
    So, how can I create a JCoRecord, or more specifically a JCoParameterList (extends JCoRecord) from the XML representation I created with JCoParameterList.toXML()? Please help!
    The JCO migration guides from SAP unfortunedly don't mention this API change at all...
    Thanks
    Andre

    Unfortunately I'm not aware of any XML parser in JCo3 that can be used. Via reflection I noticed a package private  com.sap.conn.jco.rt.XMLReader - obviously of no use. The IDoc library has XML parsing functionality, but I don't think that this can be (ab)used for your purpose (haven't done a detailed check though, just glimpsed at the API documentation).
    At some point I had implemented a SAX parser to re-create JCO.Function (or now JCoFunction) instances with parameters from an XML source (I used a repository to grab the function module interface via the name mentioned in the XML to create a "blank" instance, the rest was pretty straightforward).
    Based on [OSS note 586415 - XML methods in SAP Java Connector|https://service.sap.com/sap/support/notes/586415] I'd say you're out of luck and have to implement your own parser (this might also explain why you don't find any reference in the migration guide). I find this a bit strange though, because looking at the OSS note one would've expected a corresponding comment in the API documentation of 2.x (or they should have limited visibility of those methods) and I didn't see anything there...
    Cheers, harald

Maybe you are looking for

  • How do I link a button to another flash document?

    I am using action script 3 to make my website and all my files and done for now and complete however I have no idea how to make the buttons I created in flash link to another flash document.

  • Can't transfer music to ipod on new computer

    I just bought a new powerbook G4 and I downloaded some music from itunes. After plugging in my ipod (which shows up fine in itunes) it wont' let me transfer music to my ipod. Is there a way to transfer the music without doing the "automatic update" b

  • White type showing as black on officejet 8600

    Here is a good one... Just purchased the new Officejet 8600 and everything appeared ok with the set up.  However, the first ID document I tried to print failed to print properly. In the document, I have an number of black areas with white type.  When

  • Using View Object in Place of a Session Bean?

    I was researching on the forum approaches to storing session data and came across this interesting post: "What are you actually trying to acheive - if it is the storage of 'Session' type data for a particular user then you would create a view object

  • No messages for initial processing exist in MB90

    Hi friends,    When i try to take print from MB90 the error "No messages for initial processing exist" for Goods receipt --> others MIGO.      I maintanin the Print controls in SPRO --> MM --> IM --> Print Control.       Please help me in this issue.