Change JCO Connection

Hi,
I'm developing a DC component and I created a Model, in order to use sap function modules, but while I was creating the model , I put wrong JCO names. Can I change JCO name of an existing model?

Its a bad idea although it is possible.
Refer the following weblog.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3083%3Fpage%3Dlast%26x-order%3Ddate" [original link is broken] [original link is broken] [original link is broken]>changing [original link is broken] [original link is broken]
kk

Similar Messages

How to change JCO Connection in a WD project?

Hi to all,
I want to deploy my WD projects to another J2EE server, but I have to change the JCO connection (modeldata and metadata) in my WD projects, otherwise I can't deploy. Where can I re-assign the new jco connection?
thank you very much,
Antonio

hi Antonio,
you have to make two changes:
1) double-click on the generated adaptive-rfc-class below "Models / <Name> / Model classes" and change the property "modelInstance_defaultLogicalSystem" in the Properties-Editor for the modeldata-connection
2)double-click on the dictionary that was generated for your adaptive-rfc-call below Dictionaries and change the "Logical System Name" in the Properties-Editor for your Metadata-Connection
kr, achim
feel free to reward points, if this answers your question

Change password for JCO connections

Hi,
In our landscape we have around 80-100 applications running and there are 300-400 JCO connections on an average. We have 4 servers like this. Earlier we used to have developers user id and password for JCO connections. Now we have decided to have a universal userid and password for all the JCo connections. My question is there any way by which we can change the passwords for all the JCO connections without going to each one of them individually as it is a hectic task.
Thanks & Regards,
Vijith

Hi Vijith Kumar,
Look at the following blog:
/people/anilkumar.vippagunta2/blog/2007/02/06/dynamic-jco-creation
I guess that if you can create JCO by code you can also edit it...
Regards,
Omri

Will system change effect JCO connections.

Hi,
We are connecting to other server. So will the changes in the system reflect in the JCO connections or we have to create JCO connections individually for each application??
Is there any way to create JCOs for all applications together?
Thanks,
Zayed

If you are referring to the generated metadata and modeldata JCo destinations after creating/importing a model, it's wise to choose meaningful names for them. In my opinion a good practice is to let them reflect the type of system (ECC, CRM, etc.) that they will connect to. You can use the same names for different models. These models will then use the same JCo destinations, which has the advantage that you will only have to change 2 JCo destinations (the metadata and modeldata) when your ECC system connection parameters change for example.

JCO connection pool is exhausted

hi
I am using RFC module in my web dynpro application. When the application is used for sometime, the JCO connection will get exhusted. The JCO connection will not release itself. I can't find any method in web dynpro to release the connection manually. How can I solve this problem?

Hi,
What is scope of the connection. View properties of MODELDATA and METADATA destinations.
You can change the scope of the connection..
or
wdContext.current<BAPI INPUT>Element().modelObject().modelInstance().disconnectIfAlive();
For more ways , give a forum search.. There are a lot of close forum posts.. Gud luc..
Regards
Bharathwaj

Problem with JCo Connection Pool

Hi,
I have a problem with using an RFC Model in my WebApplication. So sometimes the access to the function block works, and sometimes it doesn't work. Now I know, that there is a problem with the connection pool. Look at this message:
com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool WD_X24_MODELDATA_DEST_CPIC_REKTO_DE_useDefinedUser is exhausted. The current pool size limit (max connections) is 10 connections.
So it looks like a problem with closing the JCo Connections after using. Do know where the problem is? Because I'm using many other function blocks with no problems.

Hello,
You need to increase the pool size via Visual Administrator.
Server 0 -> Services -> JCO RFC Connections.
Change the pool size from there. I believe a restart is in order.
Regards,
Jan

How to use a JCO connection pool in an EJB?

Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars

Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars

Error while creating a JCO Connection

Hi i am trying to create a JCO Connection from sapj2ee engine
my problem is i am getting an error connection to msg server host failed ..
When i select the Message Server the System Name and Logon Group fields are disabled and cannot be modified and the problem is there is a default system name field already present there which remains there irrespective of whther i change
the msg server...
why is this happening...
regards
Nilesh Taunk.

Hi Nilesh,
exactly follow this link for the set up in Visual Admin..
http://help.sap.com/saphelp_nw04/helpdata/en/ea/cd2e807e0e45bf9da67354f452fc05/content.htm
then refer these forums also...
Re: Metadata problem
i have already explained in step by step setting up of SLD.. in thisforum... refer this also
Re: getting a BAPI from an R/3 system
Regards
Kishor Gopinathan

JCO Connection Problem

Hi Experts,
This is not related to Java Web Dynpro directly.
We are encountering strange behavior with respect to JCo Destination.
Up to yesterday we had no problems with JCo. But when we tried to run run a Web Dynpro application, it
was not able to extract data from SAP backend.
On further investigation it was found out that JCo Destination test is failing. Following is the error when we
tried to test JCo Destination:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Client 100 is not available in this system
Backend is working fine with username and password in the client. Connection from ABAP server to
the the problematic ABAP server is also working (SM59). But connection from any Java portal to ABAP
server is not working.
Has anybody encountered this problem?
Best Regards,
Pramod

Hi Promod,
It would be some Username and password issue. If you manage to change them you issue will be resolved. Have a look at the the following useful discussion. It would be helpful for you.
JCO Connection Error
Also have a look at the following Wiki for troubleshooting the RFC Communication problems with Java Connectors.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/ep/troubleshooting%252bsap%252bjava%252bconnector%252b(JCo)
I hope this helps you.
Regards,
Gopal.

Unable to create the JCO connections in webdypro (JAVA) No SLD Connection

HI All,
In webdynpro i am unable to create standard JCo connections. create Jco connections and Maintain Jco COnnections are disabled. when i click any of the standard content of the Jco connections it displays error message No sld check. But SLD is running fine. I have checked in Visual Admin there also SLD supplier is running fine.
But i am unable to create or maintain the Standard content of the JCo Destinations.
Thank You,
Mahesh C

Hi ,
I am having all admin rights. And also i have checked in Check SLD Connection. It showing the error connection to SLD Could not opened successfully. But SLD is running fine and i have checked in Visual admin SLD datasupplier is running fine.
When i check in the log of the SLD there it is showing
#2852 11/18/2008 18:27:18.265 [SAPEngine_Application_Thread[impl:3]_29] FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Failed to initialize cluster notification. Please check your JNDI service and JMS provider for errors.
Is that i need to change the CIM content?
I could not able to get clue on this.
Thank You,
Mahesh C

JCO connection error:Couldn't create JCOClientConnection for logical System

Hi All,
We are facing a production outage issue.
We have a Federated Portal Network setup where one of our producer goes down automatically (seems on heavy load).
On this Producer server we have 3 Web Dynpro applications deployed and default trace is full with JCO connection error   saying Could   not create JCOClientConnection for logical System: CSVMR_WD_MODELDATA_DEST.
We had issue with max allowed JCO connections so we changed the below mentioned parameters for JCO connection settings in portal:
u2022     Minimum value of JCo Pool Size in total = 80
u2022     Minimum value for CPIC_MAX_CONV per SAP Web AS = 320
u2022     Maximum Number JCo Connections = 160
Please let us know if we are missing on some settings, any help in this regard is appreciated.
Regards,
Priyanka

Hi,
As you have already increased the maximum number of connections/pool size but still you are facing this problem. I would suggest you to check the web dynpro application which might not be able to release/disconnect the JCO connection.
Please check this [Thread|How to close a model object connection for Adaptive RFC?; for more details.
Regards
Puneet

JCO Connection error

Hi,
While giving the parameters for JCO connection in SLD(Technical System Type:- Web As Java) I am taking the destination Type as Application Server.
While creating the JCO connection the JCO connection is getting created but while testing the connection I am getting the following error
com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call.Do I need to take destination type as Message Server,what are the Name and Message Server for both?
Please reply.
Regards,
Pawan

Hey in SLD the WEBAS-ABAP technical system is created to identify a SAP system.The common connection properties of the SAP system(like ECC,BW,CRM)are defined under WEBAS-ABAP technical system.For each SAP system one WEBAS-ABAP technical system is created.The changing properties like username password client number of the backend system i.e SAP system are declared under the JCOs.So when you are connecting to SAP system a WEBAS-ABAP technical system should be created and JCOs should be created/specified for webdynpro applications.The JCOs will make use of the WEBAS-ABAP technical system connection properties internally from the SLD also contains the extra connection properties(client no,uname,pwd).So you have to create JCOs when you are communicating with SAP systems.
Note:No need to create JCOs for other systems(non SAP).

Jco connection :null

Hi sap gurus
I am using rfc connection for executing bapi using some jco connections. but if the jco are being used for one time it is being executed . but when we deploy application another time . the exception is received as dynamicrfcexecution error jco connection:null.
when we change the poolsize it is being . the rfc is executed for only one time.
please suggest a way to close jco connections . if already present.
Thanks & Regards
prasad

hi , logon mechanism while creating the JCO Destinations.
Is Logon Ticket
This is code what iam using for rfc access
Zhr_Emp_List_Input input = new Zhr_Emp_List_Input();
          wdContext.nodeZhr_Emp_List_Input().bind(input);
     wdContext.nodeZhr_Emp_List_Input().currentZhr_Emp_List_InputElement().setPernr("10" );
          try {
               wdContext.nodeZhr_Emp_List_Input().currentZhr_Emp_List_InputElement().modelObject().execute();
               wdContext.nodeOutput().invalidate();
          } catch (WDDynamicRFCExecuteException e) {
               wdComponentAPI.getMessageManager().reportSuccess(e.toString());
                              // TODO Auto-generated catch block
               e.printStackTrace();
          }finally {
     wdContext.currentZhr_Emp_List_InputElement().modelObject().modelInstance().disconnectIfAlive();
for the above code where Zhr_Emp_List_Input is the rfc . which will return employee details when we set the Pernr(personal number) to rfc
the exception is
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
for only one time the rfc is executing . for the other time if we increase the pool size or change the whole jco references for webdynprojava application . we are able to execute the application

JCO connection problem at web dyn pro

HI all,
I was installed sneak preview of Net weaver 6.4,
I want to do some web dynpro (java) programs which connect to back end systems.(R/3 system).
The R/3 system which I want to connect is at remote place, i have connectivity to that R/3 system using VPN connectivity. With this I am not having any problem. Since I am able to connect using User name and password, and able to do some transactions like RZ70, etc.
 I developed an application which calls COMPANY_CODE_GET_LIST (BAPI function).
for the above requirement what I did was
 (1)I created SLD setting.
 (a)Web as Java (I am not having any problem to
 Create this.
 (b) Web as ABAP.
 When i am trying to create
 This, there are some steps like i need to go to SAP log in and I need to run the transaction RZ70. For this i need to create an enter in visual administrator>JCO RFC Provider>runtime-->Bundles i need to create an entry for RFC destination as well as Repository.
 under RFC destination there are some fields which i need to enter those are (a)Program ID as mySLD (b) Gateway Host as 10.10.10.125 (c)Gateway service as sapgw00 (d)Number of processes as 1
 Under Repository (a) Application server host 10.10.10.125 (b)system number as 00 (c)Client number as 100 (d)Language as en (e)user as ABCD (f)password as 1234
I haven't choosed the check boxes Local bundle and Unicode and pressed the set button. So like this i created the RFC destinations. under the properties tab there is a property called RFC_DEFAULT_DESTINATION by default it was false so i made it as true. .
I also went to SLD Data Supplier,under Runtime tab , HTTP Settings , I mentioned
 (a)Host: pava-vis75
 (b) Port: 50000
 (c) user: administrator
 (d) password: abcd1234
 RFC Settings, I mentioned as
 (a)Gateway Host: 10.10.10.125 (which is SAP R/3 system)
 (b)Gateway Service/Host: sapgw00
 CIM Client Generation settings, as
 (a)Host: pava-vis75
 (b)Port (http/https):50000
 (c) user: administrator
 (d) Password : abcd1234
 I tested the CIMClient Test by click the the button. I got the successful message.
 Then I came back to HTTP settings and clicked the button with tilted arrow mark [This triggers data transfer to system landscape directory], for this also I got a successfully message.[data transferred successfully]
 Next I been to SAPLOGON and went to RFC Destinations by using sm59 transaction. There under TCP/IP connections i been to SLD_NUC , opened this by double clicking that and under Technical settings for Program ID I had given the ID which I created at visual administrator [JCO RFC Provider] which is mySLD , under gateway options for Gateway Host as 10.10.10.125and Gateway service as sapgw00 then i tested the connection, it was also successfully.
Then I opened the SLDAPICUST and i created a new entry for maintaining the SLD Access Data by giving some couple of entries as
 (a)Alias: vissldtest
 (b)Host Name: pava-vis75
 (c)Port: 50000
 (d) user: administrator
 (e) password: abcd1234
Then saved it.
Next I created sapmsUV0 3600/tcp entry at
WINDOWS\system32\drivers\etc\services file, and also there are some required entries which are already existing those are sapgw00 3300/tcp to sapgw99 3399/tcp , another entry starts from sapdp00s 4700/tcp to sapdp99s 4799/tcp , next entry starts from sapgw00s 4800/tcp to sapgw99s 4899/tcp and sapmsJ2E 3601/tcp .
I restarted the system, as well as server.
Now my problem is when I was trying to create JCO destination at web dynpro content administrator. For that I navigated as create JCO Destination Deployed Contentlocal-local/CompanyCodeGetList-Applications CompanyCodeGetList
I Choosed the JCO Connections tab- there are 2 entries those are
 (1) COMPANY_CODE_MODEL
 (2) COMPANY_CODE_RFC_METADATA
So I started creating connection for COMPANY_CODE_RFC_METADATA.
First one is
 General data Name : COMPANY_CODE_RFC_METADATA
 Client : 100
 I didnt changed any default JCo pool configuration.
 J2EE Cluster
 There is a check box called Use Local J2EE engine J2E on pava-vis75 so I choosed that.
 Connection Type
 Dictionary Meta Data and application Data 
 I choosed the first one.
 Then
 Msg. Server Connection
 Security
 After these, I tried to test the connection by clicking the Test Connection.
 It is saying the error as
 First time
 com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service 'sapmsUVO' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
second time
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service '?' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
Can any body please help me to solve this problem.
From past 1 week on wards I have been trying to resolve this. But in vain.

answer in your other thread on the same topic
problem in connecting JCO destination in web dynpro
(Kindly avoid double posting)
Regards
Raja

Meta JCo connection issue - cannot have 2 systems for ESS????

I have a finance R/3 system and also an HR R/3 System.
I need to be able to use the FI system for the timesheet ESS screens and the HR system for the others. I have used the iView Application parameter as documented;
(sap-wd-arfc-useSys=SAP_R3_HumanResources:FIN&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:FIN)
The JCo destinations have been configured and do work ....
However the problem is that the meta data jco connection that is used first appears to be cached and is then used going forward for every subsequent screen.
Therefore if I leave the menu screens as they are by default my timesheet screen won't work because the meta connection has been opened to the HR system and therefore the meta and data connections now don't match - even though the parameter has been set as above the configuration is ignored.
I get the following error message
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:
Accessing System DE7 is not possible because RFC Metadata was retrieved
using System DH7. Please assure you have configured the RFC Connections
properly. A Server restart may be necessary!
So if I change the menu to use the finance system then the timesheet screen will work but none of the HR screens will work. (same error with the systems reversed)
Is there any way of getting this to behave properly and make sure that the right Jco connection is used. It is very frustrating because the configuration is correct, I just need to be able to force the applications to use the the Jco destination that has been defined for the iView.
Regards
Marina

Hi, I have created new iview for Who's Who and put the below in Application Parameters:
sap-wd-arfc-useSys=SAP_R3_HumanResources:UTL&sap-wdarfc-useSys=SAP_R3_HumanResources_MetaData:UTL&sap-wd-arfc-useSys=WD_MODELDATA_DEST:UTL&sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:UTL
The Home Page Framework is working fine. but when clicking on the who's who service the below error is there:
The initial exception that caused the request to fail, was: java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) ... 75 more See full exception chain for details. System Environment Client Web Dynpro Client Type HTML Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) Version null DOM version null Client Type msie7 Client Type Profile ie6 ActiveX enabled Cookies enabled Frames enabled Java Applets enabled JavaScript enabled Tables enabled VB Script enabled Server Web Dynpro Runtime Vendor: SAP, build ID: 7.0103.20081111115141.0000 (release=NW701_03_REL, buildtime=2008-12-07:13:19:14[UTC], changelist=51958, host=pwdfm246), build date: Mon Dec 20 02:32:06 CST 2010 J2EE Engine 7.01 PatchLevel 56102. Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation Operating system AIX, version: 6.1, architecture: ppc64 Session & Other Session Locale en_US Time of Failure Wed Feb 09 14:56:21 CST 2011 (Java Time: 1297284981490) Web Dynpro Code Generation Infos sap.com/pb SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tcwddispwda No information available null sap.com/pb_api SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tcwdcorecomp No information available null Detailed Error Information Detailed Exception Chain java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.FcWiwBusinessLogicComp.onInit(FcWiwBusinessLogicComp.java:217) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicComp.onInit(InternalFcWiwBusinessLogicComp.java:414) at com.sap.xss.hr.wiw.FcWiwBusinessLogicCompInterface.onInit(FcWiwBusinessLogicCompInterface.java:115) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface.onInit(InternalFcWiwBusinessLogicCompInterface.java:298) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface$External.onInit(InternalFcWiwBusinessLogicCompInterface.java:358) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.selection.VcWiwSelectionComp.onInit(VcWiwSelectionComp.java:212) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionComp.onInit(InternalVcWiwSelectionComp.java:206) at com.sap.xss.hr.wiw.selection.VcWiwSelectionCompInterface.onInit(VcWiwSelectionCompInterface.java:162) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface.onInit(InternalVcWiwSelectionCompInterface.java:144) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface$External.onInit(InternalVcWiwSelectionCompInterface.java:220) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438) at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196) at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289) at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356) at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549) at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Change JCO Connection

Similar Messages

Maybe you are looking for