mirror of
https://github.com/Tooloop/Tooloop-Packages.git
synced 2026-04-27 20:41:37 +02:00
change folder structure and control files to newest concept
This commit is contained in:
Daniel Stock
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,157 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 2003, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Java Web Start Tools
|
||||
.\" Title: javaws.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH javaws 1 "21 November 2013" "JDK 8" "Java Web Start Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
javaws \- Starts Java Web Start\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBjavaws\fR [ \fIrun\-options\fR ] \fIjnlp\fR
|
||||
.fi
|
||||
.nf
|
||||
|
||||
\fBjavaws\fR [ \fIcontrol\-options\fR ]
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
\fIrun-options\fR
|
||||
Command-line \f3run-options\fR\&. The \f3run-options\fR can be in any order\&. See Run-Options\&.
|
||||
.TP
|
||||
\fIjnlp\fR
|
||||
Either the path of or the Uniform Resource Locator (URL) of the Java Network Launching Protocol (JNLP) file\&.
|
||||
.TP
|
||||
\fIcontrol-options\fR
|
||||
Command-line \f3control-options\fR\&. The \f3control-options\fR can be in any order\&. See Control-Options\&.
|
||||
.SH DESCRIPTION
|
||||
\fINote:\fR The \f3javaws\fR command is not available on Oracle Solaris\&.
|
||||
.PP
|
||||
The \f3javaws\fR command starts Java Web Start, which is the reference implementation of the JNLP\&. Java Web Start starts Java applications and applets hosted on a network\&.
|
||||
.PP
|
||||
If a JNLP file is specified, then the \f3javaws\fR command starts the Java application or applet specified in the JNLP file\&.
|
||||
.PP
|
||||
The \f3javaws\fR launcher has a set of options that are supported in the current release\&. However, the options may be removed in a future release\&.
|
||||
.SH RUN-OPTIONS
|
||||
.TP
|
||||
-offline
|
||||
.br
|
||||
Runs Java Web Start in offline mode\&.
|
||||
.TP
|
||||
-Xnosplash
|
||||
.br
|
||||
Does not display the initial splash screen\&.
|
||||
.TP
|
||||
-open \fIarguments\fR
|
||||
.br
|
||||
When specified, this option replaces the arguments in the JNLP file with \f3-open\fR\f3arguments\fR\&.
|
||||
.TP
|
||||
-print \fIarguments\fR
|
||||
.br
|
||||
When specified, this option replaces the arguments in the JNLP file with \f3-print\fR\f3arguments\fR\&.
|
||||
.TP
|
||||
-online
|
||||
.br
|
||||
Uses online mode\&. This is the default behavior\&.
|
||||
.TP
|
||||
-wait
|
||||
.br
|
||||
The \f3javaws\fR process does not exit until the application exits\&. This option does not function as described on Windows platforms\&.
|
||||
.TP
|
||||
-verbose
|
||||
.br
|
||||
Displays additional output\&.
|
||||
.TP
|
||||
-J\fIoption\fR
|
||||
.br
|
||||
Passes option to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&.
|
||||
.TP
|
||||
-system
|
||||
.br
|
||||
Runs the application from the system cache only\&.
|
||||
.SH CONTROL-OPTIONS
|
||||
.TP
|
||||
-viewer
|
||||
.br
|
||||
Shows the cache viewer in the Java Control Panel\&.
|
||||
.TP
|
||||
-clearcache
|
||||
.br
|
||||
Removes all non-installed applications from the cache\&.
|
||||
.TP
|
||||
-userConfig \fIproperty-name\fR
|
||||
.br
|
||||
Clears the specified deployment property\&.
|
||||
.TP
|
||||
-userConfig \fIproperty-name property-value\fR
|
||||
.br
|
||||
Sets the specified deployment property to the specified value\&.
|
||||
.TP
|
||||
-uninstall
|
||||
.br
|
||||
Removes all applications from the cache\&.
|
||||
.TP
|
||||
-uninstall \fIjnlp\fR
|
||||
.br
|
||||
Removes the application from the cache\&.
|
||||
.TP
|
||||
-print \fIimport-options\fRjnlp
|
||||
.br
|
||||
Imports the application to the cache\&.
|
||||
.SH IMPORT-OPTIONS
|
||||
.TP
|
||||
-silent
|
||||
.br
|
||||
Imports silently (with no user interface)\&.
|
||||
.TP
|
||||
-system
|
||||
.br
|
||||
Imports application to the system cache\&.
|
||||
.TP
|
||||
-codebase \fIurl\fR
|
||||
.br
|
||||
Retrieves resources from the specified codebase\&.
|
||||
.TP
|
||||
-shortcut
|
||||
.br
|
||||
Installs shortcuts if the user allows a prompt\&. This option has no effect unless the \f3-silent\fR option is also used\&.
|
||||
.TP
|
||||
-association
|
||||
.br
|
||||
Installs associations if the user allows a prompt\&. This option has no effect unless the \f3-silent\fR option is also used\&.
|
||||
.SH FILES
|
||||
For information about the user and system cache and deployment\&.properties files, see Deployment Configuration File and Properties at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/deployment/deployment-guide/properties\&.html
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Java Web Start at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/javaws/index\&.html
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,228 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 1994, 2015, Oracle and/or its affiliates. All rights reserved.
|
||||
.\"
|
||||
.\" Title: jjs
|
||||
.\" Language: English
|
||||
.\" Date: 03 March 2015
|
||||
.\" SectDesc: Basic Tools
|
||||
.\" Software: JDK 8
|
||||
.\" Arch: generic
|
||||
.\" Part Number: E38209-04
|
||||
.\" Doc ID: JSSOR
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH "jjs" "1" "03 March 2015" "JDK 8" "Basic Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
.SH "NAME"
|
||||
jjs \- Invokes the Nashorn engine\&.
|
||||
.SH "SYNOPSIS"
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
\fB\fBjjs\fR\fR\fB [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIscript\-files\fR\fR\fB] [\-\- \fR\fB\fIarguments\fR\fR\fB]\fR
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.PP
|
||||
\fIoptions\fR
|
||||
.RS 4
|
||||
One or more options of the
|
||||
\fBjjs\fR
|
||||
command, separated by spaces\&. For more information, see Options\&.
|
||||
.RE
|
||||
.PP
|
||||
\fIscript\-files\fR
|
||||
.RS 4
|
||||
One or more script files which you want to interpret using Nashorn, separated by spaces\&. If no files are specified, an interactive shell is started\&.
|
||||
.RE
|
||||
.PP
|
||||
\fIarguments\fR
|
||||
.RS 4
|
||||
All values after the double hyphen marker (\fB\-\-\fR) are passed through to the script or the interactive shell as arguments\&. These values can be accessed by using the
|
||||
\fBarguments\fR
|
||||
property (see Example 3)\&.
|
||||
.RE
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
The
|
||||
\fBjjs\fR
|
||||
command\-line tool is used to invoke the Nashorn engine\&. You can use it to interpret one or several script files, or to run an interactive shell\&.
|
||||
.SH "OPTIONS"
|
||||
.PP
|
||||
The options of the
|
||||
\fBjjs\fR
|
||||
command control the conditions under which scripts are interpreted by Nashorn\&.
|
||||
.PP
|
||||
\-cp \fIpath\fR
|
||||
.br
|
||||
\-classpath \fIpath\fR
|
||||
.RS 4
|
||||
Specifies the path to the supporting class files To set multiple paths, the option can be repeated, or you can separate each path with a colon (:)\&.
|
||||
.RE
|
||||
.PP
|
||||
\-D\fIname\fR=\fIvalue\fR
|
||||
.RS 4
|
||||
Sets a system property to be passed to the script by assigning a value to a property name\&. The following example shows how to invoke Nashorn in interactive mode and assign
|
||||
\fBmyValue\fR
|
||||
to the property named
|
||||
\fBmyKey\fR:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
\fB>> \fR\fB\fBjjs \-DmyKey=myValue\fR\fR
|
||||
\fBjjs> \fR\fB\fBjava\&.lang\&.System\&.getProperty("myKey")\fR\fR
|
||||
\fBmyValue\fR
|
||||
\fBjjs>\fR
|
||||
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
This option can be repeated to set multiple properties\&.
|
||||
.RE
|
||||
.PP
|
||||
\-doe
|
||||
.br
|
||||
\-\-dump\-on\-error
|
||||
.RS 4
|
||||
Provides a full stack trace when an error occurs\&. By default, only a brief error message is printed\&.
|
||||
.RE
|
||||
.PP
|
||||
\-fv
|
||||
.br
|
||||
\-\-fullversion
|
||||
.RS 4
|
||||
Prints the full Nashorn version string\&.
|
||||
.RE
|
||||
.PP
|
||||
\-fx
|
||||
.RS 4
|
||||
Launches the script as a JavaFX application\&.
|
||||
.RE
|
||||
.PP
|
||||
\-h
|
||||
.br
|
||||
\-help
|
||||
.RS 4
|
||||
Prints the list of options and their descriptions\&.
|
||||
.RE
|
||||
.PP
|
||||
\-\-language=[es5]
|
||||
.RS 4
|
||||
Specifies the ECMAScript language version\&. The default version is ES5\&.
|
||||
.RE
|
||||
.PP
|
||||
\-ot
|
||||
.br
|
||||
\-\-optimistic\-types=[true|false]
|
||||
.RS 4
|
||||
Enables or disables optimistic type assumptions with deoptimizing recompilation\&. Running with optimistic types will yield higher final speed, but may increase warmup time\&.
|
||||
.RE
|
||||
.PP
|
||||
\-scripting
|
||||
.RS 4
|
||||
Enables shell scripting features\&.
|
||||
.RE
|
||||
.PP
|
||||
\-strict
|
||||
.RS 4
|
||||
Enables strict mode, which enforces stronger adherence to the standard (ECMAScript Edition 5\&.1), making it easier to detect common coding errors\&.
|
||||
.RE
|
||||
.PP
|
||||
\-t=\fIzone\fR
|
||||
.br
|
||||
\-timezone=\fIzone\fR
|
||||
.RS 4
|
||||
Sets the specified time zone for script execution\&. It overrides the time zone set in the OS and used by the
|
||||
\fBDate\fR
|
||||
object\&.
|
||||
.RE
|
||||
.PP
|
||||
\-v
|
||||
.br
|
||||
\-version
|
||||
.RS 4
|
||||
Prints the Nashorn version string\&.
|
||||
.RE
|
||||
.SH "EXAMPLES"
|
||||
.PP
|
||||
\fBExample 1 \fRRunning a Script with Nashorn
|
||||
.RS 4
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
\fBjjs script\&.js\fR
|
||||
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.RE
|
||||
.PP
|
||||
\fBExample 2 \fRRunning Nashorn in Interactive Mode
|
||||
.RS 4
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
\fB>> \fR\fB\fBjjs\fR\fR
|
||||
\fBjjs> \fR\fB\fBprintln("Hello, World!")\fR\fR
|
||||
\fBHello, World!\fR
|
||||
\fBjjs> \fR\fB\fBquit()\fR\fR
|
||||
\fB>>\fR
|
||||
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.RE
|
||||
.PP
|
||||
\fBExample 3 \fRPassing Arguments to Nashorn
|
||||
.RS 4
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
\fB>> \fR\fB\fBjjs \-\- a b c\fR\fR
|
||||
\fBjjs> \fR\fB\fBarguments\&.join(", ")\fR\fR
|
||||
\fBa, b, c\fR
|
||||
\fBjjs>\fR
|
||||
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.RE
|
||||
.SH "SEE ALSO"
|
||||
.PP
|
||||
\fBjrunscript\fR
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,193 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Java IDL and RMI-IIOP Tools
|
||||
.\" Title: orbd.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH orbd 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
orbd \- Enables clients to locate and call persistent objects on servers in the CORBA environment\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBorbd\fR [ \fIoptions\fR ]
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
\fIoptions\fR
|
||||
Command-line options\&. See Options\&.
|
||||
.SH DESCRIPTION
|
||||
The \f3orbd\fR command enables clients to transparently locate and call persistent objects on servers in the CORBA environment\&. The Server Manager included with the orbd tool is used to enable clients to transparently locate and call persistent objects on servers in the CORBA environment\&. The persistent servers, while publishing the persistent object references in the naming service, include the port number of the ORBD in the object reference instead of the port number of the server\&. The inclusion of an ORBD port number in the object reference for persistent object references has the following advantages:
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
The object reference in the naming service remains independent of the server life cycle\&. For example, the object reference could be published by the server in the Naming Service when it is first installed, and then, independent of how many times the server is started or shut down, the ORBD returns the correct object reference to the calling client\&.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
The client needs to look up the object reference in the naming service only once, and can keep reusing this reference independent of the changes introduced due to server life cycle\&.
|
||||
.PP
|
||||
To access the ORBD Server Manager, the server must be started using \f3servertool\fR, which is a command-line interface for application programmers to register, unregister, start up, and shut down a persistent server\&. For more information on the Server Manager, see Server Manager\&.
|
||||
.PP
|
||||
When \f3orbd\fR starts, it also starts a naming service\&. For more information about the naming service\&. See Start and Stop the Naming Service\&.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-ORBInitialPort \fInameserverport\fR
|
||||
.br
|
||||
Required\&. Specifies the port on which the name server should be started\&. After it is started, \f3orbd\fR listens for incoming requests on this port\&. On Oracle Solaris software, you must become the root user to start a process on a port below 1024\&. For this reason, Oracle recommends that you use a port number above or equal to 1024\&.
|
||||
.SS NONREQUIRED\ OPTIONS
|
||||
.TP
|
||||
-port \fIport\fR
|
||||
.br
|
||||
Specifies the activation port where ORBD should be started, and where ORBD will be accepting requests for persistent objects\&. The default value for this port is 1049\&. This port number is added to the port field of the persistent Interoperable Object References (IOR)\&.
|
||||
.TP
|
||||
-defaultdb \fIdirectory\fR
|
||||
.br
|
||||
Specifies the base where the ORBD persistent storage directory, \f3orb\&.db\fR, is created\&. If this option is not specified, then the default value is \f3\&./orb\&.db\fR\&.
|
||||
.TP
|
||||
-serverPollingTime \fImilliseconds\fR
|
||||
.br
|
||||
Specifies how often ORBD checks for the health of persistent servers registered through \f3servertool\fR\&. The default value is 1000 ms\&. The value specified for \f3milliseconds\fR must be a valid positive integer\&.
|
||||
.TP
|
||||
-serverStartupDelay milliseconds
|
||||
.br
|
||||
Specifies how long ORBD waits before sending a location forward exception after a persistent server that is registered through \f3servertool\fR is restarted\&. The default value is 1000 ms\&. The value specified for \f3milliseconds\fR must be a valid positive integer\&.
|
||||
.TP
|
||||
-J\fIoption\fR
|
||||
.br
|
||||
Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&.
|
||||
.SS START\ AND\ STOP\ THE\ NAMING\ SERVICE
|
||||
A naming service is a CORBA service that allows CORBA objects to be named by means of binding a name to an object reference\&. The name binding can be stored in the naming service, and a client can supply the name to obtain the desired object reference\&.
|
||||
.PP
|
||||
Before running a client or a server, you will start ORBD\&. ORBD includes a persistent naming service and a transient naming service, both of which are an implementation of the COS Naming Service\&.
|
||||
.PP
|
||||
The Persistent Naming Service provides persistence for naming contexts\&. This means that this information is persistent across service shutdowns and startups, and is recoverable in the event of a service failure\&. If ORBD is restarted, then the Persistent Naming Service restores the naming context graph, so that the binding of all clients\&' and servers\&' names remains intact (persistent)\&.
|
||||
.PP
|
||||
For backward compatibility, \f3tnameserv\fR, a Transient Naming Service that shipped with earlier releases of the JDK, is also included in this release of Java SE\&. A transient naming service retains naming contexts as long as it is running\&. If there is a service interruption, then the naming context graph is lost\&.
|
||||
.PP
|
||||
The \f3-ORBInitialPort\fR argument is a required command-line argument for \f3orbd\fR, and is used to set the port number on which the naming service runs\&. The following instructions assume you can use port 1050 for the Java IDL Object Request Broker Daemon\&. When using Oracle Solaris software, you must become a root user to start a process on a port lower than 1024\&. For this reason, it is recommended that you use a port number above or equal to 1024\&. You can substitute a different port when necessary\&.
|
||||
.PP
|
||||
To start \f3orbd\fR from a UNIX command shell, enter:
|
||||
.sp
|
||||
.nf
|
||||
\f3orbd \-ORBInitialPort 1050&\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
From an MS-DOS system prompt (Windows), enter:
|
||||
.sp
|
||||
.nf
|
||||
\f3start orbd \-ORBInitialPort 1050\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
Now that ORBD is running, you can run your server and client applications\&. When running the client and server applications, they must be made aware of the port number (and machine name, when applicable) where the Naming Service is running\&. One way to do this is to add the following code to your application:
|
||||
.sp
|
||||
.nf
|
||||
\f3Properties props = new Properties();\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3props\&.put("org\&.omg\&.CORBA\&.ORBInitialHost", "MyHost");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3ORB orb = ORB\&.init(args, props);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
In this example, the naming service is running on port 1050 on host \f3MyHost\fR\&. Another way is to specify the port number and/or machine name when running the server or client application from the command line\&. For example, you would start your \f3HelloApplication\fR with the following command line:
|
||||
.sp
|
||||
.nf
|
||||
\f3java HelloApplication \-ORBInitialPort 1050 \-ORBInitialHost MyHost\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
To stop the naming service, use the relevant operating system command, such as \f3pkill\fR\f3orbd\fR on Oracle Solaris, or \fICtrl+C\fR in the DOS window in which \f3orbd\fR is running\&. Note that names registered with the naming service can disappear when the service is terminated because of a transient naming service\&. The Java IDL naming service will run until it is explicitly stopped\&.
|
||||
.PP
|
||||
For more information about the naming service included with ORBD, see Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html
|
||||
.SH SERVER\ MANAGER
|
||||
To access the ORBD Server Manager and run a persistent server, the server must be started with \f3servertool\fR, which is a command-line interface for application programmers to register, unregister, start up, and shut down a persistent server\&. When a server is started using \f3servertool\fR, it must be started on the same host and port on which \f3orbd\fR is executing\&. If the server is run on a different port, then the information stored in the database for local contexts will be invalid and the service will not work properly\&.
|
||||
.PP
|
||||
See Java IDL: The "Hello World" Example at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlExample\&.html
|
||||
.PP
|
||||
In this example, you run the \f3idlj\fR compiler and \f3javac\fR compiler as shown in the tutorial\&. To run the ORBD Server Manager, follow these steps for running the application:
|
||||
.PP
|
||||
Start \f3orbd\fR\&.
|
||||
.PP
|
||||
UNIX command shell, enter: \f3orbd -ORBInitialPort 1050\fR\&.
|
||||
.PP
|
||||
MS-DOS system prompt (Windows), enter: \f3s\fR\f3tart orbd -ORBInitialPort 105\fR\f30\fR\&.
|
||||
.PP
|
||||
Port 1050 is the port on which you want the name server to run\&. The \f3-ORBInitialPort\fR option is a required command-line argument\&. When using Oracle Solaris software, you must become a root user to start a process on a port below 1024\&. For this reason, it is recommended that you use a port number above or equal to 1024\&.
|
||||
.PP
|
||||
Start the \f3servertool\fR: \f3servertool -ORBInitialPort 1050\fR\&.
|
||||
.PP
|
||||
Make sure the name server (\f3orbd\fR) port is the same as in the previous step, for example, \f3-ORBInitialPort 1050\&.\fR The \f3servertool\fR must be started on the same port as the name server\&.
|
||||
.PP
|
||||
In the \f3servertool\fR command line interface, start the \f3Hello\fR server from the \f3servertool\fR prompt:
|
||||
.sp
|
||||
.nf
|
||||
\f3servertool > register \-server HelloServer \-classpath \&. \-applicationName\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 HelloServerApName\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
The \f3servertool\fR registers the server, assigns it the name \f3HelloServerApName\fR, and displays its server ID with a listing of all registered servers\&.Run the client application from another terminal window or prompt:
|
||||
.sp
|
||||
.nf
|
||||
\f3java HelloClient \-ORBInitialPort 1050 \-ORBInitialHost localhost\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
For this example, you can omit \f3-ORBInitialHost localhost\fR because the name server is running on the same host as the \f3Hello\fR client\&. If the name server is running on a different host, then use the -\f3ORBInitialHost nameserverhost\fR option to specify the host on which the IDL name server is running\&.Specify the name server (\f3orbd\fR) port as done in the previous step, for example, \f3-ORBInitialPort 1050\fR\&. When you finish experimenting with the ORBD Server Manager, be sure to shut down or terminate the name server (\f3orbd\fR) and \f3servertool\fR\&. To shut down \f3orbd\fR from am MS-DOS prompt, select the window that is running the server and enter \fICtrl+C\fR to shut it down\&.
|
||||
.PP
|
||||
To shut down \f3orbd\fR from an Oracle Solaris shell, find the process, and terminate with the \f3kill\fR command\&. The server continues to wait for invocations until it is explicitly stopped\&. To shut down the \f3servertool\fR, type \fIquit\fR and press the \fIEnter\fR key\&.
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
servertool(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,270 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Java Deployment Tools
|
||||
.\" Title: pack200.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH pack200 1 "21 November 2013" "JDK 8" "Java Deployment Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
pack200 \- Packages a JAR file into a compressed pack200 file for web deployment\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBpack200\fR [\fIoptions\fR] \fIoutput\-file\fR \fIJAR\-file\fR
|
||||
.fi
|
||||
.sp
|
||||
Options can be in any order\&. The last option on the command line or in a properties file supersedes all previously specified options\&.
|
||||
.TP
|
||||
\fIoptions\fR
|
||||
The command-line options\&. See Options\&.
|
||||
.TP
|
||||
\fIoutput-file\fR
|
||||
Name of the output file\&.
|
||||
.TP
|
||||
\fIJAR-file\fR
|
||||
Name of the input file\&.
|
||||
.SH DESCRIPTION
|
||||
The \f3pack200\fR command is a Java application that transforms a JAR file into a compressed pack200 file with the Java gzip compressor\&. The pack200 files are highly compressed files that can be directly deployed to save bandwidth and reduce download time\&.
|
||||
.PP
|
||||
The \f3pack200\fR command has several options to fine-tune and set the compression engine\&. The typical usage is shown in the following example, where \f3myarchive\&.pack\&.gz\fR is produced with the default \f3pack200\fR command settings:
|
||||
.sp
|
||||
.nf
|
||||
\f3pack200 myarchive\&.pack\&.gz myarchive\&.jar\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-r, --repack
|
||||
.br
|
||||
Produces a JAR file by packing and unpacking a JAR file\&. The resulting file can be used as an input to the \f3jarsigner\fR(1) tool\&. The following example packs and unpacks the myarchive\&.jar file:
|
||||
.sp
|
||||
.nf
|
||||
\f3pack200 \-\-repack myarchive\-packer\&.jar myarchive\&.jar\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3pack200 \-\-repack myarchive\&.jar\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
|
||||
The following example preserves the order of files in the input file\&.
|
||||
.TP
|
||||
-g, --no-gzip
|
||||
.br
|
||||
Produces a \f3pack200\fR file\&. With this option, a suitable compressor must be used, and the target system must use a corresponding decompresser\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3pack200 \-\-no\-gzip myarchive\&.pack myarchive\&.jar\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
.TP
|
||||
-G, --strip-debug
|
||||
.br
|
||||
Strips debugging attributes from the output\&. These include \f3SourceFile\fR, \f3LineNumberTable\fR, \f3LocalVariableTable\fR and \f3LocalVariableTypeTable\fR\&. Removing these attributes reduces the size of both downloads and installations, but reduces the usefulness of debuggers\&.
|
||||
.TP
|
||||
--keep-file-order
|
||||
.br
|
||||
Preserve the order of files in the input file\&. This is the default behavior\&.
|
||||
.TP
|
||||
-O, --no-keep-file-order
|
||||
.br
|
||||
The packer reorders and transmits all elements\&. The packer can also remove JAR directory names to reduce the download size\&. However, certain JAR file optimizations, such as indexing, might not work correctly\&.
|
||||
.TP
|
||||
-S\fIvalue\fR , --segment-limit=\fIvalue\fR
|
||||
.br
|
||||
The value is the estimated target size \fIN\fR (in bytes) of each archive segment\&. If a single input file requires more than \fIN\fR bytes, then its own archive segment is provided\&. As a special case, a value of \f3-1\fR produces a single large segment with all input files, while a value of 0 produces one segment for each class\&. Larger archive segments result in less fragmentation and better compression, but processing them requires more memory\&.
|
||||
|
||||
The size of each segment is estimated by counting the size of each input file to be transmitted in the segment with the size of its name and other transmitted properties\&.
|
||||
|
||||
The default is -1, which means that the packer creates a single segment output file\&. In cases where extremely large output files are generated, users are strongly encouraged to use segmenting or break up the input file into smaller JARs\&.
|
||||
|
||||
A 10 MB JAR packed without this limit typically packs about 10 percent smaller, but the packer might require a larger Java heap (about 10 times the segment limit)\&.
|
||||
.TP
|
||||
-E\fIvalue\fR , --effort=\fIvalue\fR
|
||||
.br
|
||||
If the value is set to a single decimal digit, then the packer uses the indicated amount of effort in compressing the archive\&. Level 1 might produce somewhat larger size and faster compression speed, while level 9 takes much longer, but can produce better compression\&. The special value 0 instructs the \f3pack200\fR command to copy through the original JAR file directly with no compression\&. The JSR 200 standard requires any unpacker to understand this special case as a pass-through of the entire archive\&.
|
||||
|
||||
The default is 5, to invest a modest amount of time to produce reasonable compression\&.
|
||||
.TP
|
||||
-H\fIvalue\fR , --deflate-hint=\fIvalue\fR
|
||||
.br
|
||||
Overrides the default, which preserves the input information, but can cause the transmitted archive to be larger\&. The possible values are: \f3true\fR, \f3false\fR, or \f3keep\fR\&.
|
||||
|
||||
If the \f3value\fR is \f3true\fR or false, then the \f3packer200\fR command sets the deflation hint accordingly in the output archive and does not transmit the individual deflation hints of archive elements\&.
|
||||
|
||||
The \f3keep\fR value preserves deflation hints observed in the input JAR\&. This is the default\&.
|
||||
.TP
|
||||
-m\fIvalue\fR , --modification-time=\fIvalue\fR
|
||||
.br
|
||||
The possible values are \f3latest\fR and \f3keep\fR\&.
|
||||
|
||||
If the value is latest, then the packer attempts to determine the latest modification time, among all the available entries in the original archive, or the latest modification time of all the available entries in that segment\&. This single value is transmitted as part of the segment and applied to all the entries in each segment\&. This can marginally decrease the transmitted size of the archive at the expense of setting all installed files to a single date\&.
|
||||
|
||||
If the value is \f3keep\fR, then modification times observed in the input JAR are preserved\&. This is the default\&.
|
||||
.TP
|
||||
-P\fIfile\fR , --pass-file=\fIfile\fR
|
||||
.br
|
||||
Indicates that a file should be passed through bytewise with no compression\&. By repeating the option, multiple files can be specified\&. There is no pathname transformation, except that the system file separator is replaced by the JAR file separator forward slash (/)\&. The resulting file names must match exactly as strings with their occurrences in the JAR file\&. If \f3file\fR is a directory name, then all files under that directory are passed\&.
|
||||
.TP
|
||||
-U\fIaction\fR , --unknown-attribute=\fIaction\fR
|
||||
.br
|
||||
Overrides the default behavior, which means that the class file that contains the unknown attribute is passed through with the specified \f3action\fR\&. The possible values for actions are \f3error\fR, \f3strip\fR, or \f3pass\fR\&.
|
||||
|
||||
If the value is \f3error\fR, then the entire \f3pack200\fR command operation fails with a suitable explanation\&.
|
||||
|
||||
If the value is \f3strip\fR, then the attribute is dropped\&. Removing the required Java Virtual Machine (JVM) attributes can cause class loader failures\&.
|
||||
|
||||
If the value is \f3pass\fR, then the entire class is transmitted as though it is a resource\&.
|
||||
.TP
|
||||
.nf
|
||||
-C\fIattribute-name\fR=\fIlayout\fR , --class-attribute=\fIattribute-name\fR=\fIaction\fR
|
||||
.br
|
||||
.fi
|
||||
See next option\&.
|
||||
.TP
|
||||
.nf
|
||||
-F\fIattribute-name\fR=\fIlayout\fR , --field-attribute=\fIattribute-name\fR=\fIaction\fR
|
||||
.br
|
||||
.fi
|
||||
See next option\&.
|
||||
.TP
|
||||
.nf
|
||||
-M\fIattribute-name\fR=\fIlayout\fR , --method-attribute=\fIattribute-name\fR=\fIaction\fR
|
||||
.br
|
||||
.fi
|
||||
See next option\&.
|
||||
.TP
|
||||
.nf
|
||||
-D\fIattribute-name\fR=\fIlayout\fR , --code-attribute=\fIattribute-name\fR=\fIaction\fR
|
||||
.br
|
||||
.fi
|
||||
With the previous four options, the attribute layout can be specified for a class entity, such as \f3class-attribute\fR, \f3field-attribute\fR, \f3method-attribute\fR, and \f3code-attribute\fR\&. The \fIattribute-name\fR is the name of the attribute for which the layout or action is being defined\&. The possible values for \fIaction\fR are \f3some-layout-string\fR, \f3error\fR, \f3strip\fR, \f3pass\fR\&.
|
||||
|
||||
\f3some-layout-string\fR: The layout language is defined in the JSR 200 specification, for example: \f3--class-attribute=SourceFile=RUH\fR\&.
|
||||
|
||||
If the value is \f3error\fR, then the \f3pack200\fR operation fails with an explanation\&.
|
||||
|
||||
If the value is \f3strip\fR, then the attribute is removed from the output\&. Removing JVM-required attributes can cause class loader failures\&. For example, \f3--class-attribute=CompilationID=pass\fR causes the class file that contains this attribute to be passed through without further action by the packer\&.
|
||||
|
||||
If the value is \f3pass\fR, then the entire class is transmitted as though it is a resource\&.
|
||||
.TP
|
||||
-f \fIpack\&.properties\fR , --config-file=\fIpack\&.properties\fR
|
||||
.br
|
||||
A configuration file, containing Java properties to initialize the packer, can be specified on the command line\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3pack200 \-f pack\&.properties myarchive\&.pack\&.gz myarchive\&.jar\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3more pack\&.properties\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3# Generic properties for the packer\&.\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3modification\&.time=latest\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3deflate\&.hint=false\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3keep\&.file\&.order=false\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3# This option will cause the files bearing new attributes to\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3# be reported as an error rather than passed uncompressed\&.\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3unknown\&.attribute=error\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3# Change the segment limit to be unlimited\&.\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3segment\&.limit=\-1\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
.TP
|
||||
-v, --verbose
|
||||
.br
|
||||
Outputs minimal messages\&. Multiple specification of this option will create more verbose messages\&.
|
||||
.TP
|
||||
-q, --quiet
|
||||
.br
|
||||
Specifies quiet operation with no messages\&.
|
||||
.TP
|
||||
-l\fIfilename\fR , --log-file=\fIfilename\fR
|
||||
.br
|
||||
Specifies a log file to output messages\&.
|
||||
.TP
|
||||
-?, -h, --help
|
||||
.br
|
||||
Prints help information about this command\&.
|
||||
.TP
|
||||
-V, --version
|
||||
.br
|
||||
Prints version information about this command\&.
|
||||
.TP
|
||||
-J\fIoption\fR
|
||||
.br
|
||||
Passes the specified option to the Java Virtual Machine\&. For more information, see the reference page for the java(1) command\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&.
|
||||
.SH EXIT\ STATUS
|
||||
The following exit values are returned: 0 for successful completion and a number greater than 0 when an error occurs\&.
|
||||
.SH NOTES
|
||||
This command should not be confused with \f3pack\fR(1)\&. The \f3pack\fR and \f3pack200\fR commands are separate products\&.
|
||||
.PP
|
||||
The Java SE API Specification provided with the JDK is the superseding authority, when there are discrepancies\&.
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
unpack200(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
jar(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
jarsigner(1)
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,94 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 2001, 2015, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 03 March 2015
|
||||
.\" SectDesc: Security Tools
|
||||
.\" Title: policytool.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH policytool 1 "03 March 2015" "JDK 8" "Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
policytool \- Reads and writes a plain text policy file based on user input through the utility GUI\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBpolicytool\fR [ \fB\-file\fR ] [ \fIfilename\fR ]
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
-file
|
||||
.br
|
||||
Directs the \f3policytool\fR command to load a policy file\&.
|
||||
.TP
|
||||
\fIfilename\fR
|
||||
The name of the file to be loaded\&.
|
||||
.PP
|
||||
\fIExamples\fR:
|
||||
.PP
|
||||
Run the policy tool administrator utility:
|
||||
.sp
|
||||
.nf
|
||||
\f3policytool\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
Run the \f3policytool\fR command and load the specified file:
|
||||
.sp
|
||||
.nf
|
||||
\f3policytool \-file \fImypolicyfile\fR\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
.SH DESCRIPTION
|
||||
The \f3policytool\fR command calls an administrator\&'s GUI that enables system administrators to manage the contents of local policy files\&. A policy file is a plain-text file with a \f3\&.policy\fR extension, that maps remote requestors by domain, to permission objects\&. For details, see Default Policy Implementation and Policy File Syntax at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.html
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-file
|
||||
.br
|
||||
Directs the \f3policytool\fR command to load a policy file\&.
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Default Policy Implementation and Policy File Syntax at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyFiles\&.html
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Policy File Creation and Management at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/PolicyGuide\&.html
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Permissions in Java SE Development Kit (JDK) at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/permissions\&.html
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Java Security Overview at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/overview/jsoverview\&.html
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Java Cryptography Architecture (JCA) Reference Guide at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec\&.html
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,294 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Remote Method Invocation (RMI) Tools
|
||||
.\" Title: rmid.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH rmid 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
rmid \- Starts the activation system daemon that enables objects to be registered and activated in a Java Virtual Machine (JVM)\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBrmid\fR [\fIoptions\fR]
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
\fIoptions\fR
|
||||
The command-line options\&. See Options\&.
|
||||
.SH DESCRIPTION
|
||||
The \f3rmid\fR command starts the activation system daemon\&. The activation system daemon must be started before activatable objects can be either registered with the activation system or activated in a JVM\&. For details on how to write programs that use activatable objects, the \fIUsing Activation\fR tutorial at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi/activation/overview\&.html
|
||||
.PP
|
||||
Start the daemon by executing the \f3rmid\fR command and specifying a security policy file, as follows:
|
||||
.sp
|
||||
.nf
|
||||
\f3rmid \-J\-Djava\&.security\&.policy=rmid\&.policy\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
When you run Oracle\(cqs implementation of the \f3rmid\fR command, by default you must specify a security policy file so that the \f3rmid\fR command can verify whether or not the information in each \f3ActivationGroupDesc\fR is allowed to be used to start a JVM for an activation group\&. Specifically, the command and options specified by the \f3CommandEnvironment\fR and any properties passed to an \f3ActivationGroupDesc\fR constructor must now be explicitly allowed in the security policy file for the \f3rmid\fR command\&. The value of the \f3sun\&.rmi\&.activation\&.execPolicy\fR property dictates the policy that the \f3rmid\fR command uses to determine whether or not the information in an \f3ActivationGroupDesc\fR can be used to start a JVM for an activation group\&. For more information see the description of the -J-Dsun\&.rmi\&.activation\&.execPolicy=policy option\&.
|
||||
.PP
|
||||
Executing the \f3rmid\fR command starts the Activator and an internal registry on the default port1098 and binds an \f3ActivationSystem\fR to the name \f3java\&.rmi\&.activation\&.ActivationSystem\fR in this internal registry\&.
|
||||
.PP
|
||||
To specify an alternate port for the registry, you must specify the \f3-port\fR option when you execute the \f3rmid\fR command\&. For example, the following command starts the activation system daemon and a registry on the registry\&'s default port, 1099\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3rmid \-J\-Djava\&.security\&.policy=rmid\&.policy \-port 1099\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
.SH START\ RMID\ ON\ DEMAND
|
||||
An alternative to starting \f3rmid\fR from the command line is to configure \f3inetd\fR (Oracle Solaris) or \f3xinetd\fR (Linux) to start \f3rmid\fR on demand\&.
|
||||
.PP
|
||||
When RMID starts, it attempts to obtain an inherited channel (inherited from \f3inetd\fR/\f3xinetd\fR) by calling the \f3System\&.inheritedChannel\fR method\&. If the inherited channel is null or not an instance of \f3java\&.nio\&.channels\&.ServerSocketChannel\fR, then RMID assumes that it was not started by \f3inetd\fR/\f3xinetd\fR, and it starts as previously described\&.
|
||||
.PP
|
||||
If the inherited channel is a \f3ServerSocketChannel\fR instance, then RMID uses the \f3java\&.net\&.ServerSocket\fR obtained from the \f3ServerSocketChannel\fR as the server socket that accepts requests for the remote objects it exports: The registry in which the \f3java\&.rmi\&.activation\&.ActivationSystem\fR is bound and the \f3java\&.rmi\&.activation\&.Activator\fR remote object\&. In this mode, RMID behaves the same as when it is started from the command line, except in the following cases:
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Output printed to \f3System\&.err\fR is redirected to a file\&. This file is located in the directory specified by the \f3java\&.io\&.tmpdir\fR system property (typically \f3/var/tmp\fR or \f3/tmp\fR) with the prefix \f3rmid-err\fR and the suffix \f3tmp\fR\&.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
The \f3-port\fR option is not allowed\&. If this option is specified, then RMID exits with an error message\&.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
The \f3-log\fR option is required\&. If this option is not specified, then RMID exits with an error message
|
||||
.PP
|
||||
See the man pages for \f3inetd\fR (Oracle Solaris) or \f3xinetd\fR (Linux) for details on how to configure services to be started on demand\&.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-C\fIoption\fR
|
||||
.br
|
||||
Specifies an option that is passed as a command-line argument to each child process (activation group) of the \f3rmid\fR command when that process is created\&. For example, you could pass a property to each virtual machine spawned by the activation system daemon:
|
||||
.sp
|
||||
.nf
|
||||
\f3rmid \-C\-Dsome\&.property=value\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
|
||||
This ability to pass command-line arguments to child processes can be useful for debugging\&. For example, the following command enables server-call logging in all child JVMs\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3rmid \-C\-Djava\&.rmi\&.server\&.logCalls=true\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
.TP
|
||||
-J\fIoption\fR
|
||||
.br
|
||||
Specifies an option that is passed to the Java interpreter running RMID\&. For example, to specify that the \f3rmid\fR command use a policy file named \f3rmid\&.policy\fR, the \f3-J\fR option can be used to define the \f3java\&.security\&.policy\fR property on the \f3rmid\fR command line, for example:
|
||||
.sp
|
||||
.nf
|
||||
\f3rmid \-J\-Djava\&.security\&.policy\-rmid\&.policy\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
.TP
|
||||
-J-Dsun\&.rmi\&.activation\&.execPolicy=\fIpolicy\fR
|
||||
.br
|
||||
Specifies the policy that RMID employs to check commands and command-line options used to start the JVM in which an activation group runs\&. Please note that this option exists only in Oracle\&'s implementation of the Java RMI activation daemon\&. If this property is not specified on the command line, then the result is the same as though \f3-J-Dsun\&.rmi\&.activation\&.execPolicy=default\fR were specified\&. The possible values of \f3policy\fR can be \f3default\fR, \f3policyClassName\fR, or \f3none\fR\&.
|
||||
.RS
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
default
|
||||
|
||||
The \f3default\fR or unspecified value \f3execPolicy\fR allows the \f3rmid\fR command to execute commands with specific command-line options only when the \f3rmid\fR command was granted permission to execute those commands and options in the security policy file that the \f3rmid\fR command uses\&. Only the default activation group implementation can be used with the default execution policy\&.
|
||||
|
||||
The \f3rmid\fR command starts a JVM for an activation group with the information in the group\&'s registered activation group descriptor, an \f3ActivationGroupDesc\fR\&. The group descriptor specifies an optional \f3ActivationGroupDesc\&.CommandEnvironment\fR that includes the command to execute to start the activation group and any command-line options to be added to the command line\&. By default, the \f3rmid\fR command uses the \f3java\fR command found in \f3java\&.home\fR\&. The group descriptor also contains properties overrides that are added to the command line as options defined as: \f3-D<property>=<value>\fR\&.The \f3com\&.sun\&.rmi\&.rmid\&.ExecPermission\fR permission grants the \f3rmid\fR command permission to execute a command that is specified in the group descriptor\&'s \f3CommandEnvironment\fR to start an activation group\&. The \f3com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR permission enables the \f3rmid\fR command to use command-line options, specified as properties overrides in the group descriptor or as options in the \f3CommandEnvironment\fR when starting the activation group\&.When granting the \f3rmid\fR command permission to execute various commands and options, the permissions \f3ExecPermission\fR and \f3ExecOptionPermission\fR must be granted to all code sources\&.
|
||||
|
||||
\fIExecPermission\fR
|
||||
|
||||
The \f3ExecPermission\fR class represents permission for the \f3rmid\fR command to execute a specific command to start an activation group\&.
|
||||
|
||||
\fISyntax\fR: The name of an \f3ExecPermission\fR is the path name of a command to grant the \f3rmid\fR command permission to execute\&. A path name that ends in a slash (/) and an asterisk (*) indicates that all of the files contained in that directory where slash is the file-separator character, \f3File\&.separatorChar\fR\&. A path name that ends in a slash (/) and a minus sign (-) indicates all files and subdirectories contained in that directory (recursively)\&. A path name that consists of the special token \f3<<ALL FILES>>\fR matches any file\&.
|
||||
|
||||
A path name that consists of an asterisk (*) indicates all the files in the current directory\&. A path name that consists of a minus sign (-) indicates all the files in the current directory and (recursively) all files and subdirectories contained in the current directory\&.
|
||||
|
||||
\fIExecOptionPermission\fR
|
||||
|
||||
The \f3ExecOptionPermission\fR class represents permission for the \f3rmid\fR command to use a specific command-line option when starting an activation group\&. The name of an \f3ExecOptionPermission\fR is the value of a command-line option\&.
|
||||
|
||||
\fISyntax\fR: Options support a limited wild card scheme\&. An asterisk signifies a wild card match, and it can appear as the option name itself (matches any option), or an asterisk (*) can appear at the end of the option name only when the asterisk (*) follows a dot (\&.) or an equals sign (=)\&.
|
||||
|
||||
For example: \f3*\fR or \f3-Dmydir\&.*\fR or \f3-Da\&.b\&.c=*\fR is valid, but \f3*mydir\fR or \f3-Da*b\fR or \f3ab*\fR is not\&.
|
||||
|
||||
\fIPolicy file for rmid\fR
|
||||
|
||||
When you grant the \f3rmid\fR command permission to execute various commands and options, the permissions \f3ExecPermission\fR and \f3ExecOptionPermission\fR must be granted to all code sources (universally)\&. It is safe to grant these permissions universally because only the \f3rmid\fR command checks these permissions\&.
|
||||
|
||||
An example policy file that grants various execute permissions to the \f3rmid\fR command is:
|
||||
.sp
|
||||
.nf
|
||||
\f3grant {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 "/files/apps/java/jdk1\&.7\&.0/solaris/bin/java";\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 "/files/apps/rmidcmds/*";\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 "\-Djava\&.security\&.policy=/files/policies/group\&.policy";\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 "\-Djava\&.security\&.debug=*";\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 "\-Dsun\&.rmi\&.*";\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3};\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
|
||||
The first permission granted allows the \f3rmid\fR tcommand o execute the 1\&.7\&.0 release of the \f3java\fR command, specified by its explicit path name\&. By default, the version of the \f3java\fR command found in \f3java\&.home\fR is used (the same one that the \f3rmid\fR command uses), and does not need to be specified in the policy file\&. The second permission allows the \f3rmid\fR command to execute any command in the directory \f3/files/apps/rmidcmds\fR\&.
|
||||
|
||||
The third permission granted, an \f3ExecOptionPermission\fR, allows the \f3rmid\fR command to start an activation group that defines the security policy file to be \f3/files/policies/group\&.policy\fR\&. The next permission allows the \f3java\&.security\&.debug property\fR to be used by an activation group\&. The last permission allows any property in the \f3sun\&.rmi property\fR name hierarchy to be used by activation groups\&.
|
||||
|
||||
To start the \f3rmid\fR command with a policy file, the \f3java\&.security\&.policy\fR property needs to be specified on the \f3rmid\fR command line, for example:
|
||||
|
||||
\f3rmid -J-Djava\&.security\&.policy=rmid\&.policy\fR\&.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
<policyClassName>
|
||||
|
||||
If the default behavior is not flexible enough, then an administrator can provide, when starting the \f3rmid\fR command, the name of a class whose \f3checkExecCommand\fR method is executed to check commands to be executed by the \f3rmid\fR command\&.
|
||||
|
||||
The \f3policyClassName\fR specifies a public class with a public, no-argument constructor and an implementation of the following \f3checkExecCommand\fR method:
|
||||
.sp
|
||||
.nf
|
||||
\f3 public void checkExecCommand(ActivationGroupDesc desc, String[] command)\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 throws SecurityException;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
|
||||
Before starting an activation group, the \f3rmid\fR command calls the policy\&'s \f3checkExecCommand\fR method and passes to it the activation group descriptor and an array that contains the complete command to start the activation group\&. If the \f3checkExecCommand\fR throws a \f3SecurityException\fR, then the \f3rmid\fR command does not start the activation group and an \f3ActivationException\fR is thrown to the caller attempting to activate the object\&.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
none
|
||||
|
||||
If the \f3sun\&.rmi\&.activation\&.execPolicy\fR property value is \f3none\fR, then the \f3rmid\fR command does not perform any validation of commands to start activation groups\&.
|
||||
.RE
|
||||
|
||||
.TP
|
||||
-log \fIdir\fR
|
||||
.br
|
||||
Specifies the name of the directory the activation system daemon uses to write its database and associated information\&. The log directory defaults to creating a log, in the directory in which the \f3rmid\fR command was executed\&.
|
||||
.TP
|
||||
-port \fIport\fR
|
||||
.br
|
||||
Specifies the port the registry uses\&. The activation system daemon binds the \f3ActivationSystem\fR, with the name \f3java\&.rmi\&.activation\&.ActivationSystem\fR, in this registry\&. The \f3ActivationSystem\fR on the local machine can be obtained using the following \f3Naming\&.lookup\fR method call:
|
||||
.sp
|
||||
.nf
|
||||
\f3import java\&.rmi\&.*; \fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 import java\&.rmi\&.activation\&.*;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 ActivationSystem system; system = (ActivationSystem)\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 Naming\&.lookup("//:port/java\&.rmi\&.activation\&.ActivationSystem");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
|
||||
.TP
|
||||
-stop
|
||||
.br
|
||||
Stops the current invocation of the \f3rmid\fR command for a port specified by the \f3-port\fR option\&. If no port is specified, then this option stops the \f3rmid\fR invocation running on port 1098\&.
|
||||
.SH ENVIRONMENT\ VARIABLES
|
||||
.TP
|
||||
CLASSPATH
|
||||
Used to provide the system a path to user-defined classes\&. Directories are separated by colons, for example: \f3\&.:/usr/local/java/classes\fR\&.
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
java(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Setting the Class Path
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,78 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Remote Method Invocation (RMI) Tools
|
||||
.\" Title: rmiregistry.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH rmiregistry 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
rmiregistry \- Starts a remote object registry on the specified port on the current host\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBrmiregistry\fR [ \fIport\fR ]
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
\fIport\fR
|
||||
The number of a \f3port\fR on the current host at which to start the remote object registry\&.
|
||||
.SH DESCRIPTION
|
||||
The \f3rmiregistry\fR command creates and starts a remote object registry on the specified port on the current host\&. If the port is omitted, then the registry is started on port 1099\&. The \f3rmiregistry\fR command produces no output and is typically run in the background, for example:
|
||||
.sp
|
||||
.nf
|
||||
\f3rmiregistry &\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
A remote object registry is a bootstrap naming service that is used by RMI servers on the same host to bind remote objects to names\&. Clients on local and remote hosts can then look up remote objects and make remote method invocations\&.
|
||||
.PP
|
||||
The registry is typically used to locate the first remote object on which an application needs to call methods\&. That object then provides application-specific support for finding other objects\&.
|
||||
.PP
|
||||
The methods of the \f3java\&.rmi\&.registry\&.LocateRegistry\fR class are used to get a registry operating on the local host or local host and port\&.
|
||||
.PP
|
||||
The URL-based methods of the \f3java\&.rmi\&.Naming\fR class operate on a registry and can be used to look up a remote object on any host and on the local host\&. Bind a simple name (string) to a remote object, rebind a new name to a remote object (overriding the old binding), unbind a remote object, and list the URL bound in the registry\&.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-J
|
||||
.br
|
||||
Used with any Java option to pass the option following the \f3-J\fR (no spaces between the \f3-J\fR and the option) to the Java interpreter\&.
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
java(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
\f3java\&.rmi\&.registry\&.LocateRegistry\fR class description at http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/registry/LocateRegistry\&.html
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
\f3java\&.rmi\&.Naming class description\fR at http://docs\&.oracle\&.com/javase/8/docs/api/java/rmi/Naming\&.html
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,117 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Java IDL and RMI-IIOP Tools
|
||||
.\" Title: servertool.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH servertool 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
servertool \- Provides an easy-to-use interface for developers to register, unregister, start up, and shut down a persistent server\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBservertool\fR \-ORBInitialPort \fInameserverport\fR [ \fIoptions\fR ] [ \fIcommands \fR]
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
\fIoptions\fR
|
||||
The command-line options\&. See Options\&.
|
||||
.TP
|
||||
commands
|
||||
The command-line commands\&. See Commands\&.
|
||||
.SH DESCRIPTION
|
||||
The \f3servertool\fR command provides the command-line interface for developers to register, unregister, start up, and shut down a persistent server\&. Command-line commands let you obtain various statistical information about the server\&. See Commands\&.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-ORBInitialHost \fInameserverhost\fR
|
||||
.br
|
||||
This options is required\&. It specifies the host machine on which the name server runs and listens for incoming requests\&. The \f3nameserverhost\fR value must specify the port on which the \f3orb\fR is running and listening for requests\&. The value defaults to \f3localhost\fR when this option is not specified\&. If \f3orbd\fR and \f3servertool\fR are running on different machines, then you must specify the name or IP address of the host on which \f3orbd\fR is running\&.
|
||||
|
||||
\fINote:\fR On Oracle Solaris, you must become a root user to start a process on a port below 1024\&. Oracle recommends that you use a port number above or equal to 1024 for the \f3nameserverport\fR value\&.
|
||||
.TP
|
||||
-J\fIoption\fR
|
||||
.br
|
||||
Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&.
|
||||
.SH COMMANDS
|
||||
You can start the \f3servertool\fR command with or without a command-line command\&.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
If you did not specify a command when you started \f3servertool\fR, then the command-line tool displays the \f3servertool\fR prompt where you can enter commands: \f3servertool >\fR\&.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
If you specify a command when you start \f3servertool\fR, then the Java IDL Server Tool starts, executes the command, and exits\&.
|
||||
.TP
|
||||
.ll 180
|
||||
register -server \fIserver-class-name\fR -classpath \fIclasspath-to-server\fR [ -applicationName \fIapplication-name\fR -args \fIargs-to-server\fR -vmargs \fIflags-for-JVM\fR ]
|
||||
Registers a new persistent server with the Object Request Broker Daemon (ORBD)\&. If the server is not already registered, then it is registered and activated\&. This command causes an installation method to be called in the \f3main\fR class of the server identified by the \f3-server\fR option\&. The installation method must be \f3public static void install(org\&.omg\&.CORBA\&.ORB)\fR\&. The install method is optional and lets developers provide their own server installation behavior, such as creating a database schema\&.
|
||||
.TP
|
||||
.ll 180
|
||||
unregister -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR
|
||||
Unregisters a server from the ORBD with either its server ID or its application name\&. This command causes an uninstallation method to be called in the \f3main\fR class of the server identified by the \f3-server\fR option\&. The \f3uninstall\fR method must be \f3public static void uninstall(org\&.omg\&.CORBA\&.ORB)\fR\&. The \f3uninstall\fR method is optional and lets developers provide their own server uninstallation behavior, such as undoing the behavior of the \f3install\fR method\&.
|
||||
.TP
|
||||
getserverid -applicationName \fIapplication-name\fR
|
||||
Returns the server ID that corresponds to the \f3application-name\fR value\&.
|
||||
.TP
|
||||
list
|
||||
Lists information about all persistent servers registered with the ORBD\&.
|
||||
.TP
|
||||
listappnames
|
||||
Lists the application names for all servers currently registered with the ORBD\&.
|
||||
.TP
|
||||
listactive
|
||||
Lists information about all persistent servers that were started by the ORBD and are currently running\&.
|
||||
.TP
|
||||
.ll 180
|
||||
locate -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR [ -endpointType \fIendpointType\fR ]
|
||||
Locates the endpoints (ports) of a specific type for all ORBs created by a registered server\&. If a server is not already running, then it is activated\&. If an \f3endpointType\fR value is not specified, then the plain/non-protected endpoint associated with each ORB in a server is returned\&.
|
||||
.TP
|
||||
.ll 180
|
||||
locateperorb -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR [ -orbid \fIORB-name\fR ]
|
||||
Locates all the endpoints (ports) registered by a specific Object Request Broker (ORB) of registered server\&. If a server is not already running, then it is activated\&. If an \f3orbid\fR is not specified, then the default value of \f3""\fR is assigned to the \f3orbid\fR\&. If any ORBs are created with an \f3orbid\fR of empty string, then all ports registered by it are returned\&.
|
||||
.TP
|
||||
orblist -serverid \fIserver-id\fR | -applicationName \fIapplication-name\fR
|
||||
Lists the \f3ORBId\fR of the ORBs defined on a server\&. An \f3ORBId\fR is the string name for the ORB created by the server\&. If the server is not already running, then it is activated\&.
|
||||
.TP
|
||||
shutdown -serverid \fIserver-id\fR | -applicationName application-name
|
||||
Shut down an active server that is registered with ORBD\&. During execution of this command, the \f3shutdown\fR method defined in the class specified by either the \f3-serverid\fR or \f3-applicationName\fR parameter is also called to shut down the server process\&.
|
||||
.TP
|
||||
startup -serverid \fIserver-id\fR | -applicationName application-name
|
||||
Starts up or activate a server that is registered with ORBD\&. If the server is not running, then this command starts the server\&. If the server is already running, then an error message is displayed\&.
|
||||
.TP
|
||||
help
|
||||
Lists all the commands available to the server through the \f3servertool\fR command\&.
|
||||
.TP
|
||||
quit
|
||||
Exits the \f3servertool\fR command\&.
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
orbd(1)
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,468 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 1999, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Java IDL and RMI-IIOP Tools
|
||||
.\" Title: tnameserv.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH tnameserv 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
tnameserv \- Interface Definition Language (IDL)\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBtnameserve\fR \fB\-ORBInitialPort\fR [ \fInameserverport\fR ]
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
-ORBInitialPort \fInameserverport\fR
|
||||
.br
|
||||
The initial port where the naming service listens for the bootstrap protocol used to implement the ORB \f3resolve_initial_references\fR and \f3list_initial_references\fR methods\&.
|
||||
.SH DESCRIPTION
|
||||
Java IDL includes the Object Request Broker Daemon (ORBD)\&. ORBD is a daemon process that contains a Bootstrap Service, a Transient Naming Service, a Persistent Naming Service, and a Server Manager\&. The Java IDL tutorials all use ORBD, but you can substitute the \f3tnameserv\fR command for the \f3orbd\fR command in any of the examples that use a Transient Naming Service\&.
|
||||
.PP
|
||||
See orbd(1) or Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html
|
||||
.PP
|
||||
The CORBA Common Object Services (COS) Naming Service provides a tree-structure directory for object references similar to a file system that provides a directory structure for files\&. The Transient Naming Service provided with Java IDL, \f3tnameserv\fR, is a simple implementation of the COS Naming Service specification\&.
|
||||
.PP
|
||||
Object references are stored in the name space by name and each object reference-name pair is called a name binding\&. Name bindings can be organized under naming contexts\&. Naming contexts are name bindings and serve the same organizational function as a file system subdirectory\&. All bindings are stored under the initial naming context\&. The initial naming context is the only persistent binding in the name space\&. The rest of the name space is lost when the Java IDL naming service process stops and restarts\&.
|
||||
.PP
|
||||
For an applet or application to use COS naming, its ORB must know the port of a host running a naming service or have access to an initial naming context string for that naming service\&. The naming service can either be the Java IDL naming service or another COS-compliant naming service\&.
|
||||
.SS START\ THE\ NAMING\ SERVICE
|
||||
You must start the Java IDL naming service before an application or applet that uses its naming service\&. Installation of the Java IDL product creates a script (Oracle Solaris: \f3tnameserv\fR) or executable file (Windows: \f3tnameserv\&.exe\fR) that starts the Java IDL naming service\&. Start the naming service so it runs in the background\&.
|
||||
.PP
|
||||
If you do not specify otherwise, then the Java IDL naming service listens on port 900 for the bootstrap protocol used to implement the ORB \f3resolve_initial_references\fR and \f3list_initial_references methods\fR, as follows:
|
||||
.sp
|
||||
.nf
|
||||
\f3tnameserv \-ORBInitialPort nameserverport&\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
If you do not specify the name server port, then port 900 is used by default\&. When running Oracle Solaris software, you must become the root user to start a process on a port below 1024\&. For this reason, it is recommended that you use a port number greater than or equal to 1024\&. To specify a different port, for example, 1050, and to run the naming service in the background, from a UNIX command shell, enter:
|
||||
.sp
|
||||
.nf
|
||||
\f3tnameserv \-ORBInitialPort 1050&\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
From an MS-DOS system prompt (Windows), enter:
|
||||
.sp
|
||||
.nf
|
||||
\f3start tnameserv \-ORBInitialPort 1050\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
Clients of the name server must be made aware of the new port number\&. Do this by setting the \f3org\&.omg\&.CORBA\&.ORBInitialPort\fR property to the new port number when you create the ORB object\&.
|
||||
.SS RUN\ THE\ SERVER\ AND\ CLIENT\ ON\ DIFFERENT\ HOSTS
|
||||
In most of the Java IDL and RMI-IIOP tutorials, the naming service, server, and client are all running on the development machine\&. In real-world deployment, the client and server probably run on different host machines from the Naming Service\&.
|
||||
.PP
|
||||
For the client and server to find the Naming Service, they must be made aware of the port number and host on which the naming service is running\&. Do this by setting the \f3org\&.omg\&.CORBA\&.ORBInitialPort\fR and \f3org\&.omg\&.CORBA\&.ORBInitialHost\fR properties in the client and server files to the machine name and port number on which the Naming Service is running\&. An example of this is shown in Getting Started Using RMI-IIOP at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi-iiop/rmiiiopexample\&.html
|
||||
.PP
|
||||
You could also use the command-line options \f3-ORBInitialPort nameserverport#\fR and \f3-ORBInitialHost nameserverhostname\fR to tell the client and server where to find the naming service\&. For one example of doing this using the command-line option, see Java IDL: The Hello World Example on Two Machines at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/tutorial/jidl2machines\&.html
|
||||
.PP
|
||||
For example, suppose the Transient Naming Service, \f3tnameserv\fR is running on port 1050 on host \f3nameserverhost\fR\&. The client is running on host \f3clienthost,\fR and the server is running on host \f3serverhost\fR\&.
|
||||
.PP
|
||||
Start \f3tnameserv\fR on the host \f3nameserverhost\fR:
|
||||
.sp
|
||||
.nf
|
||||
\f3tnameserv \-ORBInitialPort 1050\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
Start the server on the \f3serverhost\fR:
|
||||
.sp
|
||||
.nf
|
||||
\f3java Server \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
Start the client on the \f3clienthost\fR:
|
||||
.sp
|
||||
.nf
|
||||
\f3java Client \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
.SS STOP\ THE\ NAMING\ SERVICE
|
||||
To stop the Java IDL naming service, use the relevant operating system command, such as \f3kill\fR for a Unix process or \f3Ctrl+C\fR for a Windows process\&. The naming service continues to wait for invocations until it is explicitly shut down\&. Note that names registered with the Java IDL naming service disappear when the service is terminated\&.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-J\fIoption\fR
|
||||
.br
|
||||
Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&.
|
||||
.SH EXAMPLES
|
||||
.SS ADD\ OBJECTS\ TO\ THE\ NAME\ SPACE
|
||||
The following example shows how to add names to the name space\&. It is a self-contained Transient Naming Service client that creates the following simple tree\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3Initial Naming Context\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 plans\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 Personal\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 calendar\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 schedule\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
In this example, \f3plans\fR is an object reference and \f3Personal\fR is a naming context that contains two object references: \f3calendar\fR and \f3schedule\fR\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3import java\&.util\&.Properties;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3import org\&.omg\&.CORBA\&.*;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3import org\&.omg\&.CosNaming\&.*;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3public class NameClient {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 public static void main(String args[]) {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 try {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
In Start the Naming Service, the \f3nameserver\fR was started on port 1050\&. The following code ensures that the client program is aware of this port number\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 Properties props = new Properties();\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 ORB orb = ORB\&.init(args, props);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
This code obtains the initial naming context and assigns it to \f3ctx\fR\&. The second line copies \f3ctx\fR into a dummy object reference \f3objref\fR that is attached to various names and added into the name space\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 NamingContext ctx =\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NamingContextHelper\&.narrow(\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 orb\&.resolve_initial_references("NameService"));\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NamingContext objref = ctx;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
This code creates a name \f3plans\fR of type \f3text\fR and binds it to the dummy object reference\&. \f3plans\fR is then added under the initial naming context using the \f3rebind\fR method\&. The \f3rebind\fR method enables you to run this program over and over again without getting the exceptions from using the \f3bind\fR method\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 NameComponent nc1 = new NameComponent("plans", "text");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NameComponent[] name1 = {nc1};\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 ctx\&.rebind(name1, objref);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 System\&.out\&.println("plans rebind successful!");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
This code creates a naming context called \f3Personal\fR of type \f3directory\fR\&. The resulting object reference, \f3ctx2\fR, is bound to the \f3name\fR and added under the initial naming context\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 NameComponent nc2 = new NameComponent("Personal", "directory");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NameComponent[] name2 = {nc2};\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NamingContext ctx2 = ctx\&.bind_new_context(name2);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 System\&.out\&.println("new naming context added\&.\&.");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
The remainder of the code binds the dummy object reference using the names \f3schedule\fR and \f3calendar\fR under the \f3Personal\fR naming context (\f3ctx2\fR)\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 NameComponent nc3 = new NameComponent("schedule", "text");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NameComponent[] name3 = {nc3};\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 ctx2\&.rebind(name3, objref);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 System\&.out\&.println("schedule rebind successful!");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NameComponent nc4 = new NameComponent("calender", "text");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NameComponent[] name4 = {nc4};\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 ctx2\&.rebind(name4, objref);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 System\&.out\&.println("calender rebind successful!");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 } catch (Exception e) {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 e\&.printStackTrace(System\&.err);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 }\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 }\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3}\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
.SS BROWSING\ THE\ NAME\ SPACE
|
||||
The following sample program shoes how to browse the name space\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3import java\&.util\&.Properties;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3import org\&.omg\&.CORBA\&.*;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3import org\&.omg\&.CosNaming\&.*;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3public class NameClientList {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 public static void main(String args[]) {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 try {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
In Start the Naming Service, the \f3nameserver\fR was started on port 1050\&. The following code ensures that the client program is aware of this port number\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 Properties props = new Properties();\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 ORB orb = ORB\&.init(args, props);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
The following code obtains the initial naming context\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 NamingContext nc =\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 NamingContextHelper\&.narrow(\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 orb\&.resolve_initial_references("NameService"));\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
The \f3list\fR method lists the bindings in the naming context\&. In this case, up to 1000 bindings from the initial naming context will be returned in the \f3BindingListHolder\fR; any remaining bindings are returned in the \f3BindingIteratorHolder\fR\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 BindingListHolder bl = new BindingListHolder();\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 BindingIteratorHolder blIt= new BindingIteratorHolder();\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 nc\&.list(1000, bl, blIt);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
This code gets the array of bindings out of the returned \f3BindingListHolder\fR\&. If there are no bindings, then the program ends\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 Binding bindings[] = bl\&.value;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 if (bindings\&.length == 0) return;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
The remainder of the code loops through the bindings and prints outs the names\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3 for (int i=0; i < bindings\&.length; i++) {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 // get the object reference for each binding\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 org\&.omg\&.CORBA\&.Object obj = nc\&.resolve(bindings[i]\&.binding_name);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 String objStr = orb\&.object_to_string(obj);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 int lastIx = bindings[i]\&.binding_name\&.length\-1;\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 // check to see if this is a naming context\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 if (bindings[i]\&.binding_type == BindingType\&.ncontext) {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 System\&.out\&.println("Context: " +\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 bindings[i]\&.binding_name[lastIx]\&.id);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 } else {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 System\&.out\&.println("Object: " +\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 bindings[i]\&.binding_name[lastIx]\&.id);\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 }\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 }\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 } catch (Exception e) {\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 e\&.printStackTrace(System\&.err)\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 }\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3 }\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3}\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
orbd(1)
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
@@ -0,0 +1,117 @@
|
||||
'\" t
|
||||
.\" Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved.
|
||||
.\" Arch: generic
|
||||
.\" Software: JDK 8
|
||||
.\" Date: 21 November 2013
|
||||
.\" SectDesc: Java Deployment Tools
|
||||
.\" Title: unpack200.1
|
||||
.\"
|
||||
.if n .pl 99999
|
||||
.TH unpack200 1 "21 November 2013" "JDK 8" "Java Deployment Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.\" http://bugs.debian.org/507673
|
||||
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
||||
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
.ie \n(.g .ds Aq \(aq
|
||||
.el .ds Aq '
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * set default formatting
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" disable hyphenation
|
||||
.nh
|
||||
.\" disable justification (adjust text to left margin only)
|
||||
.ad l
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * MAIN CONTENT STARTS HERE *
|
||||
.\" -----------------------------------------------------------------
|
||||
|
||||
.SH NAME
|
||||
unpack200 \- Transforms a packed file produced by pack200(1) into a JAR file for web deployment\&.
|
||||
.SH SYNOPSIS
|
||||
.sp
|
||||
.nf
|
||||
|
||||
\fBunpack200\fR [ \fIoptions\fR ] input\-file \fIJAR\-file\fR
|
||||
.fi
|
||||
.sp
|
||||
.TP
|
||||
\fIoptions\fR
|
||||
The command-line options\&. See Options\&.
|
||||
.TP
|
||||
\fIinput-file\fR
|
||||
Name of the input file, which can be a pack200 gzip file or a pack200 file\&. The input can also be JAR file produced by \f3pack200\fR(1) with an effort of \f30\fR, in which case the contents of the input file are copied to the output JAR file with the Pack200 marker\&.
|
||||
.TP
|
||||
\fIJAR-file\fR
|
||||
Name of the output JAR file\&.
|
||||
.SH DESCRIPTION
|
||||
The \f3unpack200\fR command is a native implementation that transforms a packed file produced by \f3pack200\fR\f3(1)\fR into a JAR file\&. A typical usage follows\&. In the following example, the \f3myarchive\&.jar\fR file is produced from \f3myarchive\&.pack\&.gz\fR with the default \f3unpack200\fR command settings\&.
|
||||
.sp
|
||||
.nf
|
||||
\f3unpack200 myarchive\&.pack\&.gz myarchive\&.jar\fP
|
||||
.fi
|
||||
.nf
|
||||
\f3\fP
|
||||
.fi
|
||||
.sp
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
-Hvalue --deflate-hint=\fIvalue\fR
|
||||
.br
|
||||
Sets the deflation to be \f3true\fR, \f3false\fR, or \f3keep\fR on all entries within a JAR file\&. The default mode is \f3keep\fR\&. If the value is \f3true\fR or \f3false\fR, then the \f3--deflate=hint\fR option overrides the default behavior and sets the deflation mode on all entries within the output JAR file\&.
|
||||
.TP
|
||||
-r --remove-pack-file
|
||||
.br
|
||||
Removes the input pack file\&.
|
||||
.TP
|
||||
-v --verbose
|
||||
.br
|
||||
Displays minimal messages\&. Multiple specifications of this option displays more verbose messages\&.
|
||||
.TP
|
||||
-q --quiet
|
||||
.br
|
||||
Specifies quiet operation with no messages\&.
|
||||
.TP
|
||||
-lfilename --log-file=\fIfilename\fR
|
||||
.br
|
||||
Specifies a log file where output messages are logged\&.
|
||||
.TP
|
||||
-? -h --help
|
||||
.br
|
||||
Prints help information about the \f3unpack200\fR command\&.
|
||||
.TP
|
||||
-V --version
|
||||
.br
|
||||
Prints version information about the \f3unpack200\fR command\&.
|
||||
.TP
|
||||
-J\fIoption\fR
|
||||
.br
|
||||
Passes option to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&.
|
||||
.SH NOTES
|
||||
This command should not be confused with the \f3unpack\fR command\&. They are distinctly separate products\&.
|
||||
.PP
|
||||
The Java SE API Specification provided with the JDK is the superseding authority in case of discrepancies\&.
|
||||
.SH EXIT\ STATUS
|
||||
The following exit values are returned: 0 for successful completion, and a value that is greater than 0 when an error occurred\&.
|
||||
.SH SEE\ ALSO
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
pack200(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
jar(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
jarsigner(1)
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
Pack200 and Compression at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/deployment/deployment-guide/pack200\&.html
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
The Java SE Technical Documentation page at http://docs\&.oracle\&.com/javase/
|
||||
.RE
|
||||
.br
|
||||
'pl 8.5i
|
||||
'bp
|
||||
Reference in New Issue
Block a user