Madhavan Kutty

Greenhorn
+ Follow
since May 27, 2005
Madhavan likes ...
Eclipse IDE Oracle Java
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Madhavan Kutty

As far as I know, you do not need to have JRE in the client machine. You only need to specify the J2SE version in the .jnlp file and when the user clicks the link to the .jnlp file from his browser, it will check on his system whether the JRE is present or not, and if it is not, it will download it.

Do correct me if I am wrong, please..
15 years ago
After the info tag, add this :


Also, sign your jars so that they can access the local system resources. Signing is done as follows :

1. Make sure that you have an SDK 1.4.2 keytool and jarsigner in your path. These tools are located in the SDK bin directory.
2. Create a new key in a new keystore as follows:

keytool -genkey -keystore myKeystore -alias myself

You will get prompted for a information about the new key, such as password, name, etc. This will create the myKeystore file on disk.
3. Then create a self-signed test certificate as follows:

keytool -selfcert -alias myself -keystore myKeystore

This will prompt for the password. Generating the certificate may take a few minutes.
4. Check to make sure that everything is okay. To list the contents of the keystore, use this command:

keytool -list -keystore myKeystore

It should list something like:

Keystore type: jks
Keystore provider: SUN
Your keystore contains 1 entry:
myself, Tue Jan 23 19:29:32 PST 2001, keyEntry,
Certificate fingerprint (MD5):
C2:E9:BF:F9 3 F:4C:8F:3C:5F:22:9E:AF:0B:42:9D

5. Finally, sign the JAR file with the test certificate as follows:
jarsigner -keystore myKeystore test.jar myself

Repeat this step with all of your JAR files.
15 years ago
Hi,
We are dealing with a J2EE application client.
It works fine with WebSphere Application Developer(WSAD) and with the Client Binaries.

However, when we try to launch it through Web Start, we get the following exception.

*************************************************************************

Connectivity Error Occurred:
Unable to connect to Application Server. URL: corbaloc:iiop:localhost:901/
Application Server may not be running
javax.naming.NamingException: Failed to initialize the ORB. Root exception is java.lang.reflect.InvocationTargetException: java.lang.UnsatisfiedLinkError: registerNatives
at com.ibm.jvm.ExtendedSystem.registerNatives(Native Method)
at com.ibm.jvm.ExtendedSystem.<clinit>(ExtendedSystem.java:163)
at com.ibm.rmi.util.JDKBridge.setCodebaseProperties(JDKBridge.java:224)
at com.ibm.rmi.util.JDKBridge.<clinit>(JDKBridge.java:203)
at com.ibm.rmi.util.RepositoryId.<clinit>(RepositoryId.java:100)
at com.ibm.rmi.iiop.CDROutputStream.<clinit>(CDROutputStream.java:917)
at com.ibm.rmi.corba.ORB.orbParameters(ORB.java:1146)
at com.ibm.CORBA.iiop.ORB.orbParameters(ORB.java:1102)
at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1101)
at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1639)
at org.omg.CORBA.ORB.init(ORB.java:329)
at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:77)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:189)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:98)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:74)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:367)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:313)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:363)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:102)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:408)
at com.ibm.ws.naming.util.WsnInitCtx.getNameInNamespace(WsnInitCtx.java:400)
at javax.naming.InitialContext.getNameInNamespace(InitialContext.java:488)
at mars.server.ejbclients.MarsEJBClient.getInitialContextMethod(MarsEJBClient.java:60)

**************************************************************************************************

We have made sure that we have added the references to all the JARS and have signed them digitally.

We'd like to know if there is any specific method to be followed while lauching an Application Client (as opposed to a normal Java [rogram) through WebStart.

Google mentions a WebSphereClientLauncher.jar for WAS 6.0, but we were not able to find anything pertaining to WSAD 5.1.2, which we are using.

Any help with this regards will be welcome.

Thanks in advance.
15 years ago