RMI connections in Oracle Autovue server

Edit the following lines:

jvueserver.rmi.port=1099
jvueserver.socket.port=5099

This new server configuration will also need to be properly reflected in the JVUESERVER parameter specified in the APPLET tag of the HTML page embedding the AutoVue client. Note that these port numbers are not related to the HTTP port used by the WEB server.
If your AutoVue server uses a proxy server to connect to the Internet, then the proxy server name must be specified in the jvueserver.properties file.
Example:

jvueserver.http.proxyhost=my.proxyserver.com:80
jvueserver.ftp.proxyhost= my.proxyserver.com:80

Replace my.proxyserver.com with the name of the proxy server running on the server and the port with the appropriate port number. It is recommended that, except for the proxy settings, you do not change the default settings.
You should verify that the ports specified are “open” and not in use by any other process. The netstat –an program will display which ports are in use. Also, the number of consecutive ports used starting from the base value specified for RMI and Sockets will depend on the processpoolsize value set in jVueserver.properties.

No change is necessary in the AutoVue server software if the Web server is running on a port other than the default, 80. The only difference is in the client
URL.
Example:

• if the WEB server is running on port 8080, instead of the URL below:
http://jvue.company.com/jVue/jVue.html
• if the WEB browser should point to the following URL:
http://jvue.company.com:8080/jVue/jVue.html

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.