Login or Register to Ask a Question and Join Our Community


OS X OpenSource RSS

GlassFish 2.1

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X OpenSource RSS GlassFish 2.1
# 1  
Old 04-04-2009
CPU & Memory GlassFish 2.1
ImageAbout GlassFish
A production-ready, Java EE 5, open source application server. GlassFish V2 includes support for Enterprise JavaBeans (EJB) 3.0, JavaServer Faces (JSF) 1.2, JavaServer Pages (JSP) 2.1, Java Servlet 2.5, Java API for XML Web Services (JAX-WS) 2.1, Java Architecture for XML Binding (JAXB) 2.1 technologies, etc.

More from Apple...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

difference between oracle glassfish and glassfish opensource

questions. What's basically the difference between if I use the opensource and oracle glassfish (the one that requires license for production use)? Is there an evaluation period for the latter? Pls advise (0 Replies)
Discussion started by: lhareigh890
0 Replies

2. Solaris

Invalid Argument and glassfish

I tried to install glassfish on Solaris 10 and it worked fine on other instances. I got the below message bash-3.00# ./sjsas-9_1_01-solaris-sparc.bin -console bash: ./sjsas-9_1_01-solaris-sparc.bin: Invalid argument I logged on as root and the file has execute permission. So strange. Do... (1 Reply)
Discussion started by: Andrew2008
1 Replies
Login or Register to Ask a Question

LEARN ABOUT SUNOS

asupgrade

asupgrade(1m)						    Application Server Utility						     asupgrade(1m)

NAME

       asupgrade - migrates the configuration of a previously installed Sun Java System Application Server

SYNOPSIS

       asupgrade  [-c  |  --console]  [-V  --version]  [-h  |  --help]-s  |  -source  applicationserver7.x_installation  -t  --target application-
       server8.x_installation [-d | --domain domain_name -n | --nsspwdfile NSS_password_filepath -j  |	--jkspwdfile  JKS_password_filepath  -p  |
       --capwdfile CA_password_filepath]

       Use  the  asupgrade  utility to migrate the server configration and its persisted state, J2EE services, and deployed J2EE applications. The
       configuration of an installed Sun Java System Application Server 7 is migrated to the Sun Java  System  Application  Server  8  Application
       Server  installation. If the domain contains information about a deployed application and the installed application components do not agree
       with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.

       asupgrade migrates the configuration and deployed applications of a previous version of the Application Server; however, the runtime  bina-
       ries of the server are not updated. Database migrations or conversions are beyond the scope of the asupgrade command.

       Only  those  instances  that  do  not  use the Sun Java System Web Server specific features will be upgraded seamlessly. Configration files
       related to HTTP path, CGI bin, SHTML, and NSAPI plugins will not be upgraded.

       The upgrade process can also be initiated automatically at installation time using the Upgrade checkbox in the Application Server  install-
       er. After completion of the upgrade, use the Application Server 7 Uninstaller to remove the previous version of the Application Server.

       Application  archives  (.ear)  and  component  archives (.jar, .war, .rar) that are deployed in the Application Server 7 environment do not
       require any modification to run on Application Server 8. However applications and components deployed in the source server  are	repackaged
       into  new  J2EE	archives in the target server's autodeploy directory and are deployed upon server startup. Applications that do not deploy
       successfully, must use Migrationtool (asmigrate) on the application and then manually redeploy the application.

       You must specify the source and target directories for the upgrade. If the upgrade includes certificates, you must also provide	the  pass-
       words  for  the	source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application
       Server 7 uses a different certificate store format (NSS) than Application Server 8 (JSSE), the migration keys  and  certificates  are  con-
       verted  to the new format. Upon successful upgrade, an upgrate report is generated listing successfully migrated items along with a list of
       the items that could not be migrated.

OPTIONS

       -c --console	       launches the upgrade command line utility.

       -V--version		displays the version of the UpgradeTool.

       -h--help 		displays the arguments for launching the UpgradeTool.

       -s--source		identifies the installation directory for Sun Java System Application Server 7.

       -t--target		identifies the installation directory for Sun Java System Application Server 8.

       -d--domain		identifies the destination domain name for the migrated certificates.

       -n--nsspwdfile		identifies the path to the NSS password file.

       -j--jkspwdfile		identifies the path to the JKS password file.

       -p--capwdfile		identifies the path to the CA certificate password file.

EXAMPLES

       Example 1: Using asupgrade

       example% upgrade -s /home/sunas7 -t /home/sunas8

SEE ALSO

       asmigrate(1M)

Sun Java System Application Server				    March 2004							     asupgrade(1m)