Daryl Le

The application assembly tool is no longer a feature of the base WebSphere Application Server product beginning with Version 5.1. The assembly toolkit replaces the application assembly tool. The assembly toolkit is available on the IBM WebSphere Application Server Toolkit CD-ROM in the product package and at: http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q=ASTK&uid=swg24005125&loc=en_US . The assembly toolkit consists of the J2EE Perspective of the WebSphere Studio Application Developer product, including code generation capabilities.
Daryl

In order to for WAS to make authenticated connection to Tibco JMS server, we need to do the following:
1. Enable the WAS Global Security under Security section.
2. Specify alias for the Component-managed Authentication Alias and the Container-managed Authentication Alias when creating a Generic JMS Connection Factory.
3. *** VERY IMPORTANT *** Create a user id named �anonymous� with no password on the Tibco JMS server.
Apparently that WAS issues initial connection to Tibco JMS server using the anonymous user id. If this id does not exist on the Tibco JMS server, there is no hope to have anymore JMS business. Once, it establishes the initial connection, any subsequence factory connection, it will use the user id and password specified in the alias.
Note:
Before enabling WAS Global Security, you need to create a user id and password under Local OS if you are going to use Local OS as the Active User Registry.
You can create an alias under J2C Authentication Data Entries. You can find the J2C Authentication Data Entries at the bottom of Generic JMS Connection Factories page.

I am having a problem setting up WAS 5.0 that makes authenticated connections to Tibco JMS server.
If I disable the secure connection on Tibco JMS Server, my MDB bean works fine since no authentication is needed.
When I enable the secure connection on Tibco JMS Server, my MDB bean cannot be started. The error is javax.jms.JMSSecurityException: invalid name or password.
Tibco JMS Server's error log shows that WAS was trying to make a connection using an "anonymous" userid.
It appears that WAS container does not make the connection to Tibco JMS Server using the userID and password that I supplied. I defined this userID and password through J2C Authentication Data Entries and I specified the userID in Component-managed Authentication Alias and Container-managed Authentication Alias
According to the IBM WAS document, in order to use authenticated connection, I need to enable the WAS Globle Security in which I also did.
Does anyone have this similar problem or see that I'm missing something?
Thanks,
Daryl

The Application Assembly Tool ships with WAS 4.0 and WAS 5.0x. If you download and eval copy, you should be able to launch it from the bin directory. Look for the batch file named assembly.bat
NOTE: AAT is no longer a part of WAS 5.1.
Daryl

I think the Maximum Size of the ORB Service thread pool still set as 50. This is the default value.
Check under Application Servers > "your server name, e.g server1" > ORB Service > Thread Pool for this value.
In your case, you want to have a min of 30 and max of 100 session bean, you need to set the thread max size at least 100 or more. You should see the number of bean instances changed in the performance viewer up to whatever the max thread pool size that you set.
This thread pool is used to handle the connection between clients and the application server and also the communications among the components on the server side.
The reason you saw only 50 session bean instances created in the peformance viewer is that the ORB Service's max thread pool size is 50, at the most only 50 clients can concurrently connect to the server.
The container is smart enough not to create more than 50 instances of the bean since it makes no sense to create more beans than you can use.
Daryl

On Windows, you can also start/stop server or launch the admin console on a convenient launch pad named First Steps.

Correction:
Instruction for setting stateless session bean pool size on WAS 4.0 is
http://www-3.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/rn101493.3.RN.html
and WAS 5.0 is
http://publib7b.boulder.ibm.com/wasinfo1/en/info/aes/ae/rejb_ecnt.html
Daryl

Yes, you can set pool size for stateless session bean.
Follow this link for instruction to set it on WAS 4.x
http://publib7b.boulder.ibm.com/wasinfo1/en/info/aes/ae/rejb_ecnt.html
Daryl

Apparently, there is a bug in the SCEAWhiz installation. I did get the same problem when trying to generate the UCK. However, I got a response back from the Whizlabs support with the UCK within 10 minutes.
Daryl

FYI, IBM used to have a web site that shows a directory of their certified specialists, solution developers and enterprise developers etc... They dropped supporting this site at the end of last year. ???

I agreed with Burk. Some certifications are not trivial. It takes time and hard work.
Daryl

Has anyone seen the following errors:
SRVE0023E: Web Group not found
PLGN0021E: Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The web group /HelloHTML has not been defined
I am trying to invoke a simple JSP file named HelloHTML.jsp from a webserver plugin running on port 9081. The JSP file is packaged in a war file along with other html files and servlet classes. The war file has been installed as a standalone component on an app server.
Using the WebSphere Admin Console:
1. I have regenerated Webserver Plugin configuration.
2. I have defined a host alias, *:9081, in the default_host virtual host.
I got the errors when invoking the following url:
<a href="http://<host_name rel="nofollow">:9081/test/HelloHTML" target="_blank">http://<host_name>:9081/test/HelloHTML
I can invoke the html file ok using the following url:
<a href="http://<host_name rel="nofollow">:9081/test/index.html" target="_blank">http://<host_name>:9081/test/index.html
Am I missing something?
Thanks,
Daryl

No, you can't run EJB 1.0 on WebSphere App Server 4.0 (WAS40). You can either:
1. Import your 1.0 EJBs into VisualAge 4.0 (VAJ40) and then re-generate them as EJB 1.1.
2. Use Assembly Application Tool (AAT) to convert the beans from 1.0 to 1.1. See IBM InfoCenter section 6.7 Tutorial.
VAJ40 does some "magic" to make the beans look like EJB 1.1 compliant. The bean are NEVER EJB 1.1 compliant.
One way to check this out is running the Verify function of the AAT against the generated beans by VAJ40.
You'll get a lot of messages saying that the ejbs not compliant.
The strange thing is that they seems to be deployed and work fine in the WAS40.
If you have errors during the installation of the application, your application won't work.
Daryl

Originally posted by Carol Chen:
Thanks Faisal & Tony,
Regarding the EJB Guide of Nova-labs,I sent the email to them a few days ago, but I haven't got the link yet. I live in Canada, I don't know whether they have any limitation about the download.
Question from IBM 498 sample test:
I am preparing the test for IBM 488, and I did sample test of 498 (has been moved now). One question about EJB application design as following:
An auto parts assembly line is monitored by an EJB application. At random, the automated machinery takes a sample of the parts being created and checks it for the precision/accuracy of its manufacture. Any defects are recorded along with information describing the particulars of the defect. The defect should be implemented as a :
a) CMP Entity Bean
b) BMP Entity Bean
c) Stateless Session Bean
d) Stateful Session Bean
I chose the answer a). Am I right? Hope to get your guys reply.
Carol

Yes, hope it is not too late. Just joined the group. Let me know if you have other question along this line.

Thanks for the explanation. Daryl.