Creation of Properties file in j2ee visual admin
Hi,
I have followed the exact steps mentioned in the MI 2.5 installtion document for editing the entries in the <System ID>.prop files. but it is not generationg the files in the required folder in the server and sync is failing with log as " unable to open the property file".
But it worked if I copied the file manually to teh server, System_Properties file.
have you faced the same problem ever?
Thanks
Satya
Hi Satya,
If you are talking about the steps that should be completed
before testing the configuration with the url...
http://<Server>:<Port>/meSync/servlet/meSync?~sysid=<System
ID>&~login=<User
name>&password=<Password>&client=<Client>&language=<Language>&ackno
wledge=X&~test=true&
then i think version:<b>sp14</b> document is very clear...
1. In the J2EE visual administrator, choose the
service <i>Configuration Adapter</i> from the
<i>server --> services</i> menu.
2. Choose <i>RunTime</i> tab(Default).
4. Navigate to....
configurations --> apps
--> sap.com
--> com.sapmarkets.mesyncjco
--> appcfg
5. Change it to <i>edit mode</i>. choose <i>yes</i> for the popup.
6. Right Click on <i>appcfg</i> .
7. Select <i>create subnode</i>
8. Select the <i>File Entry</i> from the drop down box.
9. Give the <i>name</i> as <i><sysid>.props</i>
<sysid>= Your System id.
10. Enter the two enter each in a line in the <i>display</i>.
For eg.
ashost=<myserver>
sysnr=<sn>
<myserver>=Hostname.
<sn>=System Number.
Hope it helps.
Regards,
Maheswaran.B
Similar Messages
-
Hi fellow XI'ers,
I want to install J2EE Visual Admin tool on my laptop, but all information I can find is that I have to go to C drive \usr\sap\C11\JC00\j2ee\admin and run go.bat but...this folder does not exists on my laptop...I guess I have to install locally Netweaver or WAS? And where do I find installation files?
Best Regards,
Margarethi,
no:)
all you have to do is to copy the folder:
usr\sap\C11\JC00\j2ee\admin
to your laptop and you can use it
maybe you just have to change one path
in one of he files but try with copying first
Regards,
michal -
Canu00B4t see log with J2EE Visual Admin or Standalone Log Viewer
Bom dia!
When logging on Log Viewer, it shows de error message: Unable to invoke LogControllerFacadeMBean method:"getMetaDataOfReaders" In J2EE Visual Admin the error message after click in the item Log Viewer is Error while loading service Log Viewer
When I click in defaultTrace.trc nothing appears. The same for the others log archives listed in Log Viewer.
Can someone help me with this?
Very thanks from Spain.
In the console I see the following java exception:
Exception in thread "AWT-EventQueue-0" com.sapmarkets.bam.util.BAMRuntimeExcepti
on: Unable to invoke LogControllerFacadeMBean method: "getMetaDataOfReaders".
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeFacade
Method(AbstractLogDepot.java:225)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getMetaDataO
fReaders(AbstractLogDepot.java:303)
at com.sapmarkets.bam.view.config.AbstractViewConfiguration.getColumnInf
oFromServer(AbstractViewConfiguration.java:218)
at com.sapmarkets.bam.view.config.AbstractViewConfiguration.readSetting(
AbstractViewConfiguration.java:126)
at com.sapmarkets.bam.view.config.AbstractViewConfiguration.getColumnSet
tingForLogType(AbstractViewConfiguration.java:247)
at com.sapmarkets.bam.view.buffertable.ContentPane.obtainColumnSettings(
ContentPane.java:915)
at com.sapmarkets.bam.view.buffertable.ContentPane.<init>(ContentPane.ja
va:127)
at com.sapmarkets.bam.view.AbstractLogViewerAppplication.makeTablePane(A
bstractLogViewerAppplication.java:423)
at com.sapmarkets.bam.view.AbstractLogViewerAppplication.displayLogs(Abs
tractLogViewerAppplication.java:474)
at com.sapmarkets.bam.view.overview.OverviewFilePathTreeWrapper.openLog(
OverviewFilePathTreeWrapper.java:334)
at com.sapmarkets.bam.view.overview.OverviewFilePathTreeWrapper$TreeMous
eListener.mousePressed(OverviewFilePathTreeWrapper.java:359)
at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
3)
at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
2)
at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
2)
at java.awt.Component.processMouseEvent(Component.java:6038)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5806)
at java.awt.Container.processEvent(Container.java:2058)
at java.awt.Component.dispatchEventImpl(Component.java:4413)
at java.awt.Container.dispatchEventImpl(Container.java:2116)
at java.awt.Component.dispatchEvent(Component.java:4243)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3983)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
at java.awt.Container.dispatchEventImpl(Container.java:2102)
at java.awt.Window.dispatchEventImpl(Window.java:2440)
at java.awt.Component.dispatchEvent(Component.java:4243)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre
ad.java:273)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.
java:183)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
ad.java:173)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.invoke(Unknown Source)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeMBeanM
ethod(AbstractLogDepot.java:163)
at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeFacade
Method(AbstractLogDepot.java:206)
... 33 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sapmarkets.bam.jmx.connector.AbstractLVServer.invoke(AbstractLVSe
rver.java:184)
at com.sapmarkets.bam.jmx.connector.rmi.IntegratedConnectorClient.invoke
(IntegratedConnectorClient.java:107)
... 36 more
Caused by: javax.management.ReflectionException: No such operation: getMetaDataO
fReaders
at com.sun.jmx.mbeanserver.PerInterface.noSuchMethod(PerInterface.java:1
52)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:94)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761
... 42 more
Caused by: java.lang.NoSuchMethodException: getMetaDataOfReaders()
at com.sun.jmx.mbeanserver.PerInterface.noSuchMethod(PerInterface.java:1
50)
... 46 moreHello Ivan,
Make sure that you are using a supported JDK version as per note below:
723909 Java VM settings for J2EE 6.40/7.0
And also, make sure that the necessary environment variables are pointing to the correct JDK version.
Regards,
Rafael -
Runtime Tab missing -J2ee Visual Admin
Hi
We want to maintain the PIRWBUSER in the PMIstore (j2ee visual admin )
under
Cluster ® Server ® Services ® Destinations.
but we are not able to see the "runtime " tab as mentioned in the following help doc.
http://help.sap.com/saphelp_nw2004s/helpdata/en/30/60084136b5f423e10000000a155106/content.htm
kindly advice
regards
krishnaThanks Barry
The second times we fired it open, we were able to see the tab
thanks
regards
krishna -
Locked out of J2EE Visual Admin and other problems
I recently tried to install some Java PDK components using the SDM tool. However it failed when trying to deploy the javadoc component. Since then the following has occurred:
1. My enterprise portal website is unavailable (ERROR: 'Details: Web container not available!').
2. I can't login into the J2EE admin tool (ERROR: 'the object does not exist') using either the initially reset Admin password (as part of the original install) or 'admin'.
3. In the SAP MMC, the Server 0 instance displays yellow, with the jcontrol.exe status (under Process List) as 'some processes running' and server0 (under Process Table) status as 'starting applications'.
4. The log file on the J2EE database is 100% (not sure if this is relevant or not).
I've tried to undeploy the java components in case they are the cause of the above issues but get the following error in SDM:
Info: ***** Begin of SAP J2EE Engine Online Undeployment (J2EE) *****
No information about the J2EE engine cluster is available. The online undeployment process is continuing.
Info: ***** End of SAP J2EE Engine Online Undeployment (J2EE) *****
Error: Undeployment of SDA executed with errors.
Error: See below for details:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running. com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [server] with user name: [Administrator]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineAppOnlineUndeployerImpl.checkLoginCredentials.DMEXC)
Error: Result: error
In summary, assuming the new java components broke the EP and J2EE I can't undeploy them (because J2EE is broken) in order to fix J2EE. Damned if I do and damned if I don't.
Does anyone know why I can't login to J2EE VA, why the J2EE server only partials starts up, why the EP is not working, or how I can truncate the database log file?
I'm running EP 6.4 SP9 on W2K3.
Mike D.Hi Mike,
May be the following link will help you.
J2EE Engine start error: Database initialization failed!
Moreover, make sure that your port no to which connecting through visual admin is around 50000.
Regards,
Bharath -
J2EE Visual Admin Tool stops at 99%
Hello everyone,
I have a problem with the Visual Admintool for the J2EE of an EP 6.0 SPS12 Installation on W2k. The tool worked properly before I installed TREX 6.1.
After I connect sucessfully with the admin tool it runs slowly up to 99% and stops here. The Tree of dispatcher and his services are viewable but I cannot expand the server node.
The TREX is running fine, all services are green. The Portal is available and the MMC of Portal shows all green (all services/intances started successfully). I can login and administrate the portal. But I can't configure the TREX for the portal because I can't access the Servernode in Visual Admin.
I checked the logs for the admin tool but there are no errors. The info in admin tool shows no error too. Maybe some additional traces and logs must be first activated.
On the system is a second EP and TREX running but I stopped all other applications, restarted the portal and tried to connect with visual Admin. It stops again at 99%.
Saw some threads with a solution to modify the hosts file or change the heap size of J2EE but no one confirmed that this has helped.
Does someone has an idea what I could check next?
Regards
AlexHello Praveen,
thanks for your hint. I checked the note which is very old and only for release 6.20 (I'm on 6.40). I found a similar error in my logs but this error was produced by a failed login and was not releted to my problem. I checked again my logs after but could not find any helpful entry here.
Some more ideas? Looks like a candidate for a OSS message to SAP again.
Regards
Alex -
Configuring name server in j2ee visual admin
hi all
i found the go.bat file in the following path in my system
/usr/sap/EEP/JC00/j2ee/admin/go.bat
now i want to run that "go.bat" but i don't know how to run this in linux machine but my portal server is installed in linux machine.so, can any one help me how to run that file in order to configure name server .
and also can any one tell me how to find out the server name and port number in order to fill the following format in name sererver
tcpip://<%nameserver%>:portnumber
plzz help me out
Thks&Rgds
Gnanahi dominlik
yeah go file is there but while running the following was displayed
[root@entegdt26 admin]# ls
adminCFG.properties go go.jar lib logviewer-standalone
cfg go.bat launcher log
[root@entegdt26 admin]# sh go
go: line 7: /usr/java/bin/java: No such file or directory
[root@entegdt26 admin]#
can u tell me how to mark it as executable using chmod coz i am not aware of linux
its very very urgent help out only one day i've time with in this i've to configure trex name server and create index in ep
awaiting for reply
Regards
gnana -
Error access J2EE Visual Admin
I've just completed installing the SAP NetWeaver 04 Sneak Preview. Unfortunately, TREX is not running (or maybe even installed). I've tried to login to the J2EE admin tool to specify the TREX server but I get the following message:
Unable to lookup connection default
http://server:50004/msgserver/test/logon returned empty list of connection parameters.
Port 50004 is the P4 port for the Java install. I've tried port 50000 but get the same message. Does anyone have any idea?Hi Robert,
Just so there is no confusion - there is no TREX included with the Sneak Preview packages currently available on SDN.
Regards,
Kathy Meyers
SDN -
Is there configuration setting file that shows settings in visual admin
Is there a configuration file or text file that shows visual admin parameter settings that i view without starting up visual administration.
Thanks
Weyland YutaniThe use of Visual Administrator is the fact, that those "configurations" are spread across the filesystem and in the database. You could do everything done with VA also by hand by editing .properties files or change XML files.
Markus -
Can't locate .properties file on Visual Admin
Hello,
I have created an RID.properties file inside a DynPro application under src/packages/... and I am able to load it and get it's attributes from the DynPro code.
So far so good...
As far as I know this properties file can be viewd and modifed on the Visual Admin under:
Configuration Adapter -> webdynpro...
I've browsed all the folders at this location and couldn't locate my .properties file. So where is it...?
Royi think you only want to access and maintain the properties on server side...
ok, check out
http://help.sap.com/saphelp_nw04/helpdata/en/b8/aa343e32ff1033e10000000a114084/content.htm
for an example how to access the properties from your wdp app.
i suggest loading all props into a specific context node and corresponding attributes. perhaps there are better ways.
Now sth. uncomfortable:
Be careful when you redeploy your app. All properties are overwritten with the ones you defined locally.
you also cant delete the config on local side, it would be deleted on server, too. (at least i think so) -
By mistake i deleted the Propertysheet.properties file in VC admin
Hi All,
I have an issue in visual composer, I did the following.. then i got the error when I logged into VC that "Proxy error : Server error : Failed to read models list"
1. Log on to Visual Administrator.
2. In the left panel, make sure the Global Configuration tab is chosen.
3. In the tree, expand the Services node and choose the Configuration Adapter service. In
the main pane, in the Display configuration tab, the Configurations tree is displayed.
4. Expand the development server node to display the client workspaces.
Under client workspaces i have gone to my login name under that by mistake i deleted the Propertysheet.properties file.
Then i refreshed the my model name, then the Propertysheet.properties file came.
Still I am getting the error. Can you help me out... Its very urgent to resolve this.. I will give points for good answers.
Thanks
Suresh.Hi,
does this only happen for your user or for all?
Anja -
Can't launch Visual Admin. - go.jar file is missing
Hi Guys..
I try to launch visual admin directly using go.bat but getting an error that go.jar is missing.
can I copy it from somewhere.. ?
Cheersgo.jar file is executable file, go.bat has reference to this go.jar. Thus, when you click go.bat it basically calling go.jar only
If you have taken any back earlier try to restore. As you know, VA contains all configuration details specific to your configuration/build so i do not think it's good idea to use some other system's go.jar file.
-Sekhar -
Configuration (properties file) in Visual Administrator
Hi,
properties files can be edited in Visual Adminstrator (under Configuration Adapter) and there is also a description field. I thougt it would be filled with comments in the properties file, but the description field is always empty. It is possible to fill this field?
Regards,
RomanRe: Storing constant values in OSB captures the earlier discussion.
Re: OSB: What is best practice for reading configuration information
Please go through above links and see they suit your needs.
Thanks
Manoj -
MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin
Hi,
I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
This is the setup I used:
JDBC Version "2.0 (with XA support)
JDBC 2.0 Compliant:
object factory: com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
datasource type: XADataSource
xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
On the additional tab:
databaseName=fldev_jj
portNumber=1433
serverName=dbsrv61
user=fldev_jj
password=******
Even added the url, but that made no difference. Chose Vendor SQL,
and have initial connections set to 1. This url worked when used
with a version 1.x datasource.
What can I try to do to resolve this?
Full exception:
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
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:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
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:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
... 43 more
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
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:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
... 43 more
at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
... 33 more
at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
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:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at javax.management.MBeanException.writeObject(MBeanException.java:126)
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:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
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:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)Leaving the object factory empty is absolutely part of the solution.
I can now start the data source and it can get a connection.
The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
The problem with that is that I'm no longer sure it uses XA transactions...
Will do more testing...
Very helpful reply Yuri!
Thanks -
N4S testdrive Visual Admin passowrd for J2ee
Hanns, Markus
I have the N4S system installed and running looking to use the Visual Admin program do you guys have any idea what the password is set for on this testdrive system for Administrator ?
I have seen a couple of threads and help articles to reset this password but figured you guys might know what was set when the created the N4S testdrive system.
Thanks for your time
Edited by: FC7600 on Apr 5, 2010 11:06 PM
Edited by: FC7600 on Apr 5, 2010 11:07 PMRainer
I tried that one already it did not work. get user Authorization error.
All the other are set to that.
I might need to go through the reset procedure.
EDIT
You made me think more about ID used got it fixed thanks.
Edited by: FC7600 on Apr 6, 2010 5:25 PM
Maybe you are looking for
-
Randomly occurring error while starting MDB transaction
We have been seeing a strange intermittent problem with MDBs in a clustered WLS 9.1 environment. Our cluster consists of two managed servers, each of which runs on a separate Windows machine, and our application is targeted to both. We use container
-
Trying to decide between Vision Standard and Pro 2013 and all I need to be sure of is if the Standard version has the Gantt Chart template in it or not? Does any know???
-
Reset code is being rejected. It will not allow m...
Skype rejected my password, I received a new code to access account via ail from skype, skype will not recognise code. Please help....
-
Business area is not assign to gl account
Dear SAP Expert I have Business Area set up in my SAP. After I done the MB1A (Goods receipt), they will 4 postings created. 3 of then got assigned with the Business Area but one is not. Why this will happend ? I want all the account / postings be ass
-
Hi, i need some help. i would like to know how can i do to change automatically the status of a load from a infopackage from yellow to green for executing in a process chain . thanks for the help and sorry for my bad english. Edited by: Jose Guedez