In this article on Sun Developer Network, a Java Technology Evangelist suggests the best troubleshooting practices for Java SE 6 issues during deployment.
Hi Experts.
I need to install one help library in Fedora 13 and I got the installation document for it:
---------------------------------------------------
users need their own J2EE web application server to be able
to complete this installation. The server must support J2EE - JSP... (3 Replies)
Hi,
I need to develop a script which will deploy my web application binary(.war) file in the jboss application server.
I also need to take the back up of the existing binary file and rename the same with current date and then deploy the new binary from my specified location.
The same... (1 Reply)
Dear All,
I have been deploying my web application binary on Jboss application server manually on 13 servers with 2 instances on each server. i.e. 26 instances. It is really becoming time consuming to deploy the application manually.
I am looking for a script which would deploy my binary file... (1 Reply)
Heya,
my university department wants to deploy a UNIX based system instead of various unnetokred windows PCs. We are trying to build a terminal server solution on either FreeBSD,Solaris or Debian Linux. The system would mostly run office applications on X11 and file sharing (with Samba). In... (4 Replies)
I have developed an application in Eclipse and created a JAR File for the same. I deployed the JAR File in UNIX environment and while executing the same I get the following Error:
(dstdbxx1:/export/home/edi_proc/PSON_Automation)$ls
LOG PSON ... (2 Replies)
DACS.JAVA(7) DACS Miscellaneous Information DACS.JAVA(7)NAME
dacs.java - DACS Java support
DESCRIPTION
This document describes support for Java provided by DACS.
To enable Java support, DACS must be configured using the --enable-java flag. It may also be necessary to specify the location of the Java
commands and include files. See dacs.install(7)[1].
Note
Java support is currently very limited and should be considered experimental. It is currently only possible to call dacsauth(1)[2] and
dacscheck(1)[3] using the Java Native Interface (JNI) provided. The command line arguments to both of these commands are exactly as
documented in their manual pages. Each argument is passed as a String.
The code is not thread-safe and is probably not suitable for being called many times within a particular process due to assumptions it
makes about dynamic memory allocation.
There are no immediate plans to improve or extend Java support. Using the existing capability to build the JNI layer, however, it
should not be difficult for an experienced Java programmer to build upon the example Java code provided.
With Java support enabled, building DACS will copy the JNI shared library and a .jar file to the library directory (default:
/usr/local/dacs/lib), and the JNI include files to the include directory (default: /usr/local/dacs/include).
The tools/java/jni distribution directory contains a simple script called javarun that demonstrates how to run dacsauth or dacscheck as a
Java application. For example, to validate the Unix password for user somebody, run (as root):
./javarun dacsauth -m unix suff -user somebody -prompt
DIAGNOSTICS
The return codes are as documented in the command's manual page.
AUTHOR
Distributed Systems Software (www.dss.ca[4])
COPYING
Copyright2003-2012 Distributed Systems Software. See the LICENSE[5] file that accompanies the distribution for licensing information.
NOTES
1. dacs.install(7)
http://dacs.dss.ca/man/dacs.install.7.html
2. dacsauth(1)
http://dacs.dss.ca/man/dacsauth.1.html
3. dacscheck(1)
http://dacs.dss.ca/man/dacscheck.1.html
4. www.dss.ca
http://www.dss.ca
5. LICENSE
http://dacs.dss.ca/man/../misc/LICENSE
DACS 1.4.27b 10/22/2012 DACS.JAVA(7)