WebSphere Express in a VMware guest - Cloning

I am sure that you can save lot of time & efforts if you proceed
installing WAS after the clone.

Khaja.

On May 21, 2:14 am, tim.w...@schwans.com wrote:
> We are getting ready to deploy a new site, using WebSphere Express hosted in a VMware ESX environment. One of the nice features of VMware guests is that one can clone a machine; I'd like to be able to build on instance of my host machine and then clone additional from there.
>
> The hosts will be running RHEL v.4 Update 6, WAS Express 6.1 and Apache Web Server. I can clone the first instance, and re-naming the OS is quite simple; here's my question. If I install WAS before the clone, is there a way to reconfigure the install to use the new machine name for the server/cell/etc? Is there a list of files that contain the name I can edit, or an administrative task I can perform? Or am I best off doing the clone before the install? I am working on building the response files for the installation(s) and I could have the necessary files ready and actually probably script the install, but as always, I am looking for the option that will give me the best/quickest results.
>
> Thanks in advance.
>
> Tim

MQ Link

From: scag...@us.ibm.com
Date: May 16, 4:12 pm
Subject: MQ Link
To: ibm.software.websphere.application-server

I just set up an MQ link using the following doc:

 http://www.ibm.com/developerworks/forums/thread.jspa?
threadID=178523&tstart=0&messageID=14016821

I did not secure the link, becuase I do not need SSL security

How do I test the link (other than using a MDB)

Can I view MQ files from within WAS using the MQ link.  Can I see the
contents or view the number of messages on the queue.

If not, in what way can I test the MQ link ?

Fwd: Best Practices

ibm.software.websphere.application-server

Ok, here's the short story. I work at a place where we use Websphere
Application Server with Oracle. Our environment consists of around 8
servers, each with Websphere along with one of the servers as Oracle.

Our architects along with help from IBM originally setup these WAS
servers to use the IP Address instead of a hostname or FQHN, etc.
Since these clusters are setup on a private LAN to talk to one
another, this works how it is. We usually have them talking with one
another either thru their own switch or VLAN, using IP Addresses.

We have a partnership with another company who does testing (sort of
like our QA department) and they hired this guy who claims he knows
everything that takes the servers we setup and installs/integrates it
into their environment to test. Even though he's never touched
websphere before he got hired, he's now trying to demans we change our
long process of using FQHN instead, saying it's best practice and
claims that IBM Websphere documentation says to avoid using IP
Addresses, even though IBM from the beginning helped us setup our
clusters with IP Addresses. (To make that portion short, our actual
client who uses this environment will not allow a separate DNS for
FQHN). I also believe that if you want to go by best practices, you
would skip setting these up using the /etc/hosts like this guy wants
done on each server but this is just making a simple setup more
complicated cause we gave them a new cluster and they refuse to put
the backend IP Addresses we used on its own VLAN or buy a switch.

Can anyone tell me if there's any documentation that actually states
in writing that IBM says to avoid using IP addresses when setting up
WAS, even though I've seen some documentation use IP Addresses instead
of hostnames when setting up clusters?

And trust me, I've been a Unix admin for a long time, I understand
"best practices" but I also believe in, "if it isn't broke, don't fix
it". I have a case against this guys demands so we don't have to
change our whole process of delivery and we want their test
environment exactly how production is setup but I hate it when people
might be blurting out things that aren't necessarily true.

Thanks.

Newsgroups: ibm.software.websphere.application-server
From: "Ben_" <re...@newsgroup.com>
Date: Sat, 17 May 2008 09:27:51 +0200
Local: Sat, May 17 2008 3:27 am
Subject: Re: Best Practices

they hired this guy who claims he knows everything

Exporting your frustation here won't help... :-)

> saying it's best practice and claims that IBM Websphere documentation says
> to avoid using IP Addresses

Generally speaking, it's indeed recommended to use DNS aliases instead
of IP
addresses or real hostname for the flexibility it brings in terms of
network
and system management.

A drawback of this I can think of is that it opens the server to DNS
spoofing attacks.

> even though IBM from the beginning helped us

It's not a guarantee. I saw IBM consultants do weird things to say
the
least... :-)

> they refuse to put the backend IP Addresses we used on its own VLAN or buy
> a switch.

I don't understand what you mean here.

If they prefer to use hostname, they can put it in your/their DNS.

> Can anyone tell me if there's any documentation that actually states in
> writing that IBM says to avoid using IP addresses when setting up WAS,
> even though I've seen some documentation use IP Addresses instead of
> hostnames when setting up clusters?

There is enough formal documentation where use of IP or hostname are
mentionned, be it in Technotes or InfoCenter.

E.g. this Technote explains how to change it:
http://www-1.ibm.com/support/docview.wss?uid=nas1c6cf048cd783df7b8625....

WebSphere Technical Exchange Webcast

WebSphere Application Server Administration with Jython
Presenter(s): Bob Gibson
Time: 28 May 2008, 11 AM EDT (GMT-4)

Insufficient WebSphere® Application Server administrative scripting
examples written in Jython are available for review and learning.
Techniques, idioms, and some complete Jython scripts will be
described, discussed, and made available.

Please call into the phone conference and join the e-meeting 10
minutes early.

Web conference

URL:

https://www-1.ibm.com/collaboration/webconferences/center/meetingdetails.jsp?meetingId=1A34A21E8DAB9DB6A294EDA871BC1BA8

Password: wste28may

Phone conference
Confirmation number: 4249220
US Toll-free number: 888-293-6953
International number: 719-325-2177
IBM only tie-line: 650-2041
Belgium 0800-75239
Denmark 8088-6220
France 0800-903255
Germany 0800-181-9023
Italy 800-873-740
Netherlands 0800-023-5304
Norway 800-19666
Portugal 800-819-729
Spain 900-947-605
Sweden 02-079-0880
Switzerland 0800-564-398
South Africa 0800-980-989
United Kingdom 0808-101-1147

Unable to start MDB Listener... ..javax.security.auth.login.LoginException

From: lna...@us.ibm.com
Date: May 14, 6:33 pm
Subject: Unable to start MDB
Listener... ..javax.security.auth.login.LoginException
To: ibm.software.websphere.application-server

Problem when I start application containing MDBs & ListenerPorts.  5
MDBs tied to 5 ListenerPorts within the application, 4 MDBs/
ListenerPorts start fine with no problem, 5th causes the following
exception and then stops the ListenerPort.  Problem occurs whether
Global Security is turned on or off.

I am using WAS ND v6.1.0.13

 5/14/08 9:03:40:921 EDT 0000001c MDBListenerIm W   WMSG0019E: Unable
to start MDB Listener ProcessSubmission, JMSDestination jms/
Q_SubmissionReceipt : java.security.PrivilegedActionException:
javax.security.auth.login.LoginException: No LoginModules configured
for

        at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.jav­
a:12 2)

        at
com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.ja­
va:3 67)

        at
com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java­:
727 )

        at
com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:
650)

        at
com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImp­
l.ja va:634)

        at
com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:227)

        at
com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBLis­
tene rManagerImpl.java:872)

        at
com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerMan­
ager Impl.java:830)

        at
com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListen­
erIm pl.java:188)

        at
com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgr­
Impl .java:1253)

        at
com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEven­
t(De ployedApplicationImpl.java:1148)

        at
com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedAppli­
cati onImpl.java:243)

        at
com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedAppli­
cati onImpl.java:238)

        at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicat­
ionI mpl.java:844)

        at
com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(Applicatio­
nMgr Impl.java:950)

        at com.ibm.ws.runtime.component.ApplicationMgrImpl
$AppInitializer.run(Applicat­ionM grImpl.java:2120)

        at com.ibm.wsspi.runtime.component.WsComponentImpl
$_AsynchInitializer.run(WsCo­mpon entImpl.java:342)

        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)

This seems to have worked fine in my RSA development environment
running against a WAS v6.1 (non-ND) server but is failing once
deployed to the WAS ND v6.1.0.13 server environment.

Has anyone seen this before or can provide any suggestions/solutions?

Could this be due to some code/action unique to the failing MDB?

Newsgroups: ibm.software.websphere.application-server
From: Infyniti <infyn...@gmail.com>
Date: Wed, 14 May 2008 09:52:59 EDT
Local: Wed, May 14 2008 6:52 pm
Subject: Re: Unable to start MDB
Listener... ..javax.security.auth.login.LoginExcepti­on

lnayda wrote:

Problem when I start application containing MDBs & ListenerPorts. 5
MDBs tied to 5 ListenerPorts within the application, 4 MDBs/
ListenerPorts start fine with no problem, 5th causes the following
exception and then stops the ListenerPort. Problem occurs whether
Global Security is turned on or off.

Does the JAAS alias for the queue connection factory for the 5th MDB
is same as the rest of them.

If yes, then check if the id has access to the queue. Also double
check both the QCF and QD attributes for that MDB.

Thanks

Anant

Newsgroups: ibm.software.websphere.application-server
From: lna...@us.ibm.com
Date: Wed, 14 May 2008 11:10:48 EDT
Local: Wed, May 14 2008 8:10 pm
Subject: Re: Unable to start MDB
Listener... ..javax.security.auth.login.LoginExcepti­on

By setting the "Mapping-configuration alias" to
"DefaultPricipalMapping" on the 5th MDB it now works.

I'm not sure why it is acting this way because even though the MQ
security attributes for the 4th Queue and the configuration of the MDB/
ListenerPort is identical to the 5th, I only had problems on the 5th
and needed to set the "Mapping-configuration alias" on the 5th to cure
this problem. ???

"Mapping-configuration alias" is (none) on the 4th but it is working
fine.

Happy that it works now, and thank you for your advice and
assistance.

Re: Question about the Trial and Beta version of WebSphere

On May 14, 7:42 pm, jmarch...@cobbcounty.org wrote:
> Does anyone know if the trial can be reinstalled once the time is up?  I'm only interested in using it to learn.  Reinstalling can only help me.  Not trying to circumvent any license.  I don't know what it says.  Or, does anyone know if the beta is "crippled" in any way?  I would simply use the community edition, but it is lacking functionality like portlets.  I can use it to create the applications and test, but I need to learn to use the real product.
>
> Thanks.

The only way to use Websphere application server Beta or Trial
versions after time is up without reinstalling the WAS product you
need to change Date & time settings of the system and reboot the
Operating System, try this if doesn't works please let me know.

Regards,
Khaja

Sun Java System Directory Server 6.2 Database May Become Corrupted

1. Impact

A race condition may cause database pages for Sun Java System Directory Server to not sync to disk, resulting in possible Directory Server database corruption. Depending on which pages are affected, the impact may vary.

2. Contributing Factors
This issue can occur in the following releases for all platforms (Solaris 8, 9, and 10 SPARC and x86 Platforms, Linux, Windows, HP-UX):

* Sun Java System Directory Server Enterprise Edition 6.2

Note: Directory Server 6.1, 6.0, 5.2 and 5.1 are not affected by this issue.

To determine if the Directory Server running on a system is affected, the following command can be used:

$ dsadm -V

If the output contains the version string 6.2, the system is affected.

3. Symptoms
Depending on which database page is affected and which operation tries to access it, the resulting error messages can be different, but in the most frequent cases a message similar to the following is logged:

DEBUG - conn=-1 op=-1 msgId=-1 - libdb: PANIC: fatal region error detected; run recovery

4. Workaround
There is no workaround for this issue. Please see the Resolution section below.

5. Resolution
This issue is addressed in the following releases:

Native Package Versions:

* Solaris 9 and 10 with SPARC patch 125276-07 or later
* Solaris 9 x86 with patch 125277-07 or later
* Solaris 10 x86 and x64 with patch 125278-07 or later
* Linux with patch 125309-07 or later
* Windows with patch 125311-07 or later

PatchZIP (Compressed Archive) versions:

* Solaris 9 and 10 with SPARC patch 126748-04 or later
* Solaris 9 x86 with patch 126749-04 or later
* Solaris 10 x86 and x64 with patch 126750-04 or later
* Linux with patch 126751-04 or later
* Windows with patch 126753-04 or later
* HP-UX with patch 126752-04 or later

Note: After patches have been applied: Since the database corruption can be present but undetected, it is recommended to rebuild the database by exporting to an ldif file and reimporting the ldif file. In a replicated environment, all servers need to be rebuilt or reinitialized. Export/Import and initializing servers in a replicated environment is documented in the DSEE reference guide at:

http://docs.sun.com/app/docs/doc/820-2491/bcaim?a=view


For More details:

http://sunsolve.sun.com/search/document.do?assetkey=1-66-235361-1