[ravlad]

Hi all, im trying to test java api integration.
Information described in datamanagement.pdf looks not completed.

After adding some jar's to java project and compiling Example3 -
GetEntityNames program failed with next messages:

Could not logon to machine t3://localhost:7001 as user guest
javax.naming.NamingException: Invalid provider URL

[size=4]javax.naming.NamingException

: Invalid provider URL

at com.evermind.server.rmi.RMILocation.createRMILocat ion(RMILocation.java:79)

at com.evermind.server.rmi.RMILocation.createRMILocat ion(RMILocation.java:56)

at com.evermind.server.rmi.RMIClient.getLocations(RMIClient.java:528)

at com.evermind.server.rmi.RMIClient.getDomain(RMIClient.java:507)

at com.evermind.server.rmi.RMIClient.getContext(RMIClient.java:418)
.......

my glog.properties (i put it into {home} dir):

appserver=xxx.xxx.xxx.xxx
appserver.port=7001
appserver.protocol=t3://
glog.app.server.name=oas
maybe someone allready meet such messages?

[nick.polites]

Is you application server up and running? From the error it appears that it's not or is not accepting connections. Check your weblogic console.log file under /otm/logs/weblogic for additional errors in the startup.

[chrisplough]

Also, there appears to be a mismatch in your property files -- are you running WebLogic or OAS as your OTM application server?

--Chris

[ravlad]

server is running, also otm runned on oracle app server, but i think its not a problem.

i'm trying to connect to application server which are runned on another computer, in my glog.properties i specify ip address of otm server, but java client trying to connect to local machine, why? i dont understand.

[ravlad]

one more, i comment string
glog.app.server.name=oas
and after that program exit with another exeption
java.lang.NoClassDefFoundError: weblogic/security/service/PrivilegedActions

so, looks like property file successfully finded.

[chrisplough]

Are you running WebLogic or OAS for your OTM application server? If you're running WebLogic, then you'll need extra libraries and jar files available for this to work (hence the error you received). If you're running OAS, then your other properties should be different - to include a different communications protocol and port.

--Chris

[ravlad]

OAS

--Alex

[chrisplough]

In that case, your properties should look like:

appserver=xxx.xxx.xxx.xxx
appserver.port=23791
appserver.protocol=ormi://
glog.app.server.name=oas

--Chris