See Issue #2 below. Many of our corporate paying customers are having
problems with us (attempting) to make external connections. We need to
decide how we want to solve (disable?) this for these customers.
Ken
attached mail follows:
My apology if I have sent this email to the wrong email alias or if you
are not suppose to be getting these emails with GlassFish/SJSAS questions.
IHAC with a couple urgent GlassFish/SJSAS questions (below) that I have
spent much time researching and not getting any where or knowing who to
send my questions to.
Please review the 2 detailed questions below and provide answers or
point me in the right direction.
Thank you for your help.
Regards,
Tim Nguyen
CSD Architect
Sun PS - Software PSD
*GlassFish/SJSAS Questions:
--------------------------------------*
*Question #1:*
*How can Sun customers cleanly unbundle and/or uninstall the Sun Java
System Message Queue Broker (imq) package that's shipped/bundled and
installed with the Sun Java System Application Server v9.1?
**Background for Question #1:*
IHAC that needs to be able to run 30 to 40 instances of SJSAS v9.1 on
their T5220 box (e.g. 1 SJSAS instance in each local zone) to leverage
the virtualization and isolation features in Solaris 10. To do this,
they must slim down their Solaris 10 and SJSAS v9.1 installations in
order to conserve on memory and/or CPU resources on each of their
Solaris 10 whole root local zones as they unable to use sparse root zones.
They are using WebSphere MQ v6.0 as their JMS MQ Broker and they do not
wish to use the Sun Java System Message Queue Broker (iqm) package
that's shipped/bundled, installed, and configured to run with the Sun
Java System Application Server v9.1 on their Solaris 10 zones. In order
to disable the iqm processes that are started whenever an SJSAS instance
starts in a local zone, the customer configured the Java Message Service
Type as REMOTE and specified a single imq instance running in a global
zone as the default JMS host for their Java Messaging Service in SJSAS.
However, they have a strict requirement to use Sun N1 SPS for fast
provisioning, installing, and configuring their SJSAS DAS and instances
onto the Solaris 10 local zones and they must slim down the SJSAS
installation to get rid of unwanted software bundle packages (e.g. such
as Sun Java System Message Queue Broker). This also gets rid of the
requirement for them to keep an instance of the imq service running just
so SJSAS instances can be started correctly as they are configured to
look for a REMOTE Java Message Service.
Bottom line, the customer wants to unbundle, uninstall, and get rid of
the Sun Java System Message Queue Broker (imq) package for all their
SJSAS installations and want a clean way to do this through N1 SPS.
Please advise on how to unbundle, uninstall, and delete the imq
processes in order to help the customer implement this request of a
slimmed down SJSAS installation.
*Question #2:*
*How can Sun customers customize and tune the SJSAS Admin Console web
application in order to improve the performance of this relatively slow
Web UI application?
*
*Background for Question #2:*
The customer sees a very slow & non-responsive SJSAS Admin Console
application that pops-up a dialog to require users to login through
their corporate Proxy Server in order to access the SJSAS Admin Console
web app. Furthermore, it appears the SJSAS Admin Console web
application looks for resources (e.g. static images, DTD's, and links)
on Sun's external web sites and this slows down the start-up and access
to the SJSAS Admin Console application.
The customer has already configured the Admin Server JVM heap size to be
1 GB and they just simply want the SJSAS Admin Console web application
to be more responsive (i.e. faster remdering) and NOT require users to
login to their corporate proxy server in order to access resources (e.g.
static images, DTD's, and links) on Sun's external web sites.