Find That Sometimes The Webstart Java Client Does Not Get The Application Specific Start Arguments Passed (Doc ID 1618916.1)

Last updated on JULY 11, 2016

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.2.2 and later
Information in this document applies to any platform.

Symptoms

Sporadically WebStart Java Client does not get application specific start arguments given by command line URL parameters into Java Client mask: "Connection to Agile e6".
Values from predefined jacc_xx.defaults file will be used instead

Steps to Reproduce:
----------------------------

1.)
On Oracle Agile e6 App Server // WebLogic Server deploy a modified WebStart Java Client with custom files
- jacc_cus.jnlp
- jacc_cus.defaults

in addition to existing standard files
- jacc.jnlp
- jacc.defaults

2.) On Client desktop create a cmd script calling WebStart Java Client as follows:
"C:\Program Files (x86)\Java\jre7\bin\javaws.exe" "https://example.com:7104/Jacc/jacc_cus.jnlp?-a=plmprod&-h=example.de&-d=16087&-u=%username%"  (***)

3.) Execute cmd script to start WebStart Java Client

4.) Sporadically receive error - Java Client mask: "Connection to Agile e6" does not get fields filled - e.g.


- field Benutzer/User ... (with given URL argument -u=%username% (current OS user))

- field Anwendung/Application ... (with given URL argument -a=plmprod , but value from configured jacc_cus.defaults instead

Hint (***)

The WebStart Java Client call via cmd script is used instead of using the Browser to be able to dial with necessary Java 7 installation in parallel.

Java Webstart executable javaw.exe in version Java7 is used to download the Java Client appliaction, but Java 6 is used to run the Java Client.

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms