| Author |
Message
|
| mrlazy |
 Posted: Mon Oct 16, 2006 10:43 am Post subject: Quesion reg. MQWorkflow Web-Clients |
 |
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi all,
We have MQ Workflow 3.4 server in test and prod. But our MQ Workflow web-clients are on sun boxes, which no other apps on it, except the Workflow web-client. Now we are planning to move those clienttn apps alone to a new AIX boxes and get rid of sun boxes completely.
Can I have two MQWF web-clients connected to same MQ Workflow server from two diff boxes? (in this case, I wanted to see if the app on AIX and the on sun box connect to same MQWF server) Or is it strictly one client to one server? No changes are being made to server at this time.
If possible, could you please let me know any precautions to take before I actually migrate the app? (jmac & venny, your valuable thoughts plz)
Thanks a lot! |
|
| Back to top |
|
 |
| jmac |
| Posted: Mon Oct 16, 2006 11:02 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
My most valuable thought:
V3.4 is out of support.
If I understand you correctly, I think you should be able to do what you are asking, however, this is not one of my areas of great expertise with the product. Hopefully Venny will weigh in.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mrlazy |
| Posted: Mon Oct 16, 2006 11:07 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi Jmac,
| Quote: |
| V3.4 is out of support. |
Yes we upgraded one of our environments to 3.6, but for the others before we though of starting to upgrade, we had a few high prioirty things to care of. So once we get that done, we'll start upgrading from 3.4 to 3.6.
I guess I can wait until venny responds to my question.
Thanks Jmac. |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Mon Oct 16, 2006 11:37 am Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Yes, You can connect multiple clients running on different boxes to single workflow server. No changes required on the Server side.
You are going to add one more client to the server as you did with other one. We have couple of applications configured that way.
Thanks,
-Mahesh |
|
| Back to top |
|
|
| mrlazy |
| Posted: Tue Oct 17, 2006 5:44 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Thanks for your reply!
Just one more question:
Is MQ Workflow WebClient 3.4 compatible with WAS 6? Because I'm currently trying to install it on a box with WAS 6 on it, but I could not find WAS 6 in the options while configuring. We have either WAS 3,4, or 5 and others as the options, but not WAS 6.
Please let me know any other option available if that is not possible. We are planning to migrate to 3.6, but certainly not in the next 2-3 months.
Thanks a lot! |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Oct 17, 2006 6:00 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Not sure I have ever used 3.4 on WAS 6 but I have definitely used 3.5 and 3.6
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Oct 18, 2006 6:09 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Or, anyone else has any idea if 3.4 web-client can be used with WAS 6?
Because I got the following error when I tried to create a configuration:
FMC33746I Creating the Web Client files ...
FMC33938I Creating 'fmcohcli.war'
FMC33687I /usr/java131/jre/bin/jar cMf fmcohcli.war -C webpages/ .
sh: /usr/java131/jre/bin/jar: not found.
FMC33939E Creation of 'fmcohcli.war' failed.
FMC33201I Configuration Commands Menu:
l ... List
s ... Select
c ... Create
x ... Exit Configuration Commands Menu
I checked the directory and found all the files in place (compared to an existing system).
Kindly help me out  |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Oct 18, 2006 6:44 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I am reasonably certain, that I did not use the MQWF configuration tool to do the deploy automatically with V3.5. I had the config generated, then deployed manually using WAS Admin Console.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Oct 18, 2006 7:25 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
jmac, I too am planning to do the same. But for that, we should have the fmcohcli.war generated while creating a configuration, right?
I am having an issue when this war file is generated. What we did in earlier installations was to create an 'ear' file with the above generated 'war' file and then deploy using WAS admin console. (usually done by my colleague)
I was able to connect to the Workflow server with the configuration that I created(using fmcautil), but since we don't have the war file, not able to deploy the ear file to appserver.
Is it ok if we copy the ear file from our old working directory to the current directory(diff box)? Please let me know if I'm not clear enough in expressing my doubt.
Thanks a lot and appreciate your help. |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Oct 18, 2006 7:57 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Not my area of expertise (deployment). I have always deployed the generated war file.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kotha |
| Posted: Wed Oct 18, 2006 9:02 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| Quote: |
| is it ok if we copy the ear file from our old working directory to the current directory(diff box)? Please let me know if I'm not clear enough in expressing my doubt. |
I think it is OK to use the old one if the configuration is same. |
|
| Back to top |
|
|
| chintu |
| Posted: Wed Oct 18, 2006 9:57 am Post subject: |
|
|
Acolyte
Joined: 27 Dec 2004
Posts: 64
|
It should be ok to use the same EAR/WAR file. If you want to change the configuration that the webclient points to, change the AgentConfiguration value in the WebClient.properties in the ....\webclient\WEB-INF directory prior to deployment.
I think WAS 6 requires an app to be J2EE 1.4 compliant. If you get a deployment error, then "migrate" the webclient project in RAD(or other IDEs) to J2EE 1.4 |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Oct 18, 2006 11:38 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
| Thanks a lot for your feedback, guys! |
|
| Back to top |
|
|
| hos |
| Posted: Thu Oct 19, 2006 3:12 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
| You can try the option 'OTHER AppServer' (not WebSphere) in the configuration tool in order to get a war file created (e.g. for TomCat). You then might be able to create a suitable ear file for WebSphere 6.0. But deployment definitely has to be done manually and not by MQWF tools as administration of WAS 6.0 differs from WAS 5.x. |
|
| Back to top |
|
|
|
|
