Use the package-appclient command to pack the application client container libraries and jar files into an appclient.jar file. The created file is located at appserver_install_dir/lib/appclient/appclient.jar. The appclient.jar file provides an application client container package targeted at remote hosts that do not contain a server installation.
The appclient.jar archive contains native code and can be used on a target machine that is of similar architecture as the machine where it was produced. So, for example, an appclient.jar produced on a Solaris SPARC platform cannot be used on a Windows client machine.
After copying the appclient.jar file to a remote location, unjar it to get a set of libraries and jar files in the appclient directory
After unjarring on the client machine, modify appclient_install_dir/config/asenv.conf (asenv.bat for Windows) as follows:
set AS_WEBSERVICES_LIB to appclient_install_dir/lib
set AS_NSS to appclient_install_dir/lib (appclient_install_dir\bin for Windows)
set AS_IMQ_LIB to appclient_install_dir/imq/lib
set AS_INSTALL to appclient_install_dir
set AS_JAVA to your JDK 1.4 home directory
set AS_ACC_CONFIG to appclient_install_dir/config/sun-acc.xml
Modify appclient_install_dir/config/sun-acc.xml as follows:
Ensure the DOCTYPE file references appclient_install_dir/lib/dtds
Ensure that target-server address attribute refrences the server machine.
Ensure that target-server port attribute refrences the ORB port on the remote machine.
Ensure that log-service references a log file; if the user wants to put log messages to a log file.
Modify appclient_install_dir/bin/appclient (appclient.bat for Windows) as follows:
change token %CONFIG_HOME% to appclient_install_dir/config
Sun often provides developers with early access to new technologies, which allows developers to evaluate with them as soon as possible. Unfortunately, new technologies are prone to changes and standardization often results in interface incompatibility from previous versions.
To make reasonable risk assessments, developers need to know how likely an interface is to change in future releases. To aid developers in making these assessments, interface stability information is included on some manual pages for commands, entry-points, and file formats.
The more stable interfaces can safely be used by nearly all applications, because Sun will endeavor to ensure that these continue to work in future minor releases. Applications that depend only on Standard and Stable interfaces should reliably continue to function correctly on future minor releases (but not necessarily on earlier major releases).
The less stable interfaces allow experimentation and proto-typing, but should be used only with the understanding that they might change incompatibly or even be dropped or replaced with alternatives in future minor releases.
"Interfaces" that Sun does not document (for example, most kernel data structures and some symbols in system header files) may be implementation artifacts. Such internal interfaces are not only subject to incompatible change or removal, but we are unlikely to mention such a change in release notes.