| Author |
Message
|
| mike_mq |
 Posted: Mon Mar 15, 2004 8:49 am Post subject: Problems with Admin Server, while using Authentication Exit. |
 |
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
Hello,
I am getting problems in starting administration server. This was happend when I try to
implement Authentication Exit. I have followed the steps from support pack. ie,
a) copied Authentication.java and AuthenticationConstants.java from
c:\WebSphere MQ Workflow\smp\java\authexit directory to c:\WebSpehre MQ Workflow\smp\
java\authexit\com\ibm\workflow\java\exit
b) copied Credentials.java and Authentication.java from c:\WebSphere MQ Workflow\smp\
java\authexit directory to c:\WebSpehre MQ Workflow\smp\java\authexit\com\ibm\workflow\
java\exit\sample
c) from c:\WebSphere MQ Workflow\smp\java\authexit, compiled the files
javac -classpath c:\WebSphere MQ Workflow\bin\JAVA3404\fmcojagt.jar com\ibm\workflow\
java\exit\sample\*.java
javac -classpath c:\WebSphere MQ Workflow\bin\JAVA3404\fmcojagt.jar;. com\ibm\workflow\
java\exit\Authentication.java
d) created jar file
jar -cvf fmcaexit.jar com
e) set the classpath in the environment the MQWF Administration Server is going to run
set classpath=c:\WebSphere MQ Workflow\smp\java\authexit\fmcaexit.jar;c:\WebSphere MQ
Workflow\BIN\JAVA3404\fmcojagt.jar;c:\WebSphere MQ Workflow\BIN\JAVA3404\fmcojapi.jar;
f) enabled the Java AuthenticationExit by executing:
fmczchk -c inst:m,RTAuthenticationExitTypeServer,JAVA -y <Cfg-ID>
then I restarted the system and started the services using windows services. When I logon
to the webclient, it is giving Timeout occurred FMC00014E.
Also, fmcautil is not connecting to Administration Server.
Can anybody help me out to start my administration server. It was working fine before I
started working on Authentication Implementation.
Regards,
Mike. |
|
| Back to top |
|
 |
| Ratan |
| Posted: Mon Mar 15, 2004 9:42 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I got a similar problem. I think Setting the Workflow Server to be started as ./LocalSystem in windows services solved the issue.
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Mar 15, 2004 9:49 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
How did you start your server?
Did you start it using command line or using the windows services?
The reason I am asking this is because you said
| Quote: |
set classpath=c:\WebSphere MQ Workflow\smp\java\authexit\fmcaexit.jar;c:\WebSphere MQ
Workflow\BIN\JAVA3404\fmcojagt.jar;c:\WebSphere MQ Workflow\BIN\JAVA3404\fmcojapi.jar;
|
This ENV variable would only survive the terminal window you set it on and not to the workflow server's CLASSPATH. You should set it on the system's env variable |
|
| Back to top |
|
|
| mike_mq |
| Posted: Mon Mar 15, 2004 10:10 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
I tried starting the server from command prompt using fmcautil.
ratan... how do I use./LocalSystem to start the server?
Thanks!
Mike |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Mar 15, 2004 10:21 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
use a local administrator account for 'Log on As' in Windows services
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Mar 15, 2004 10:56 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
I tried starting the server from command prompt using fmcautil.
|
You CANNOT start the workflow server using admin utility. To start the server from command line you should start it by fmcamain |
|
| Back to top |
|
|
| mike_mq |
| Posted: Mon Mar 15, 2004 11:17 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
when I type fmcamain on the command prompt, it is saying
"The service process could not connect to the service controller. (0x427).
fmcsys.log file:
3/15/2004 2:06:30 PM FMC31050E An error has occurred which has terminated processing.
3/15/2004 2:06:30 PM
Exception Class : FmcExitException
Error ID : A2
Error Description :
No Java-Authentication Exit available: could not access authentication method.
fmcerr.log:
WebSphere MQ Workflow 3.4 Error Report
Report creation = 3/15/2004 2:06:29 PM
Related message = FMC31050E An error has occurred which has terminated processing.
Error location = File=e:\v340\src\fmcaauth.cxx, Line=161, Function=FmcAuthenticationExit::Init
Error data =
Exception Class : FmcExitException
Error ID : A2
Error Description :
No Java-Authentication Exit available: could not access authentication method.
I am unable to start the workflow admin server. I did added the jarfiles into systems environment classpath. Still I am unable to login. Can anybody help me out.
Thanks.,
Mike. |
|
| Back to top |
|
|
| mike_mq |
| Posted: Mon Mar 15, 2004 11:40 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
When I disable the AuthenticationExit by executing
fmczchk -c inst:m,RTAuthenticationExitTypeServer -y <Cfg-ID> and I am able to login and administration server is up and running. So I might be wrong in implementing AuthenticationExit. I am guessing, there should be wrong in setting the classpath. Because, the log says
"could not access authentication method".
Can anybody tell me where I went wrong in my procedure.
Regards,
Mike. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Mar 15, 2004 11:40 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
To start the workflow server from command line on Windows:
| Code: |
| start fmcamain -c -y <config Id> |
|
|
| Back to top |
|
|
| vennela |
| Posted: Mon Mar 15, 2004 1:01 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Post your authentication exit source code and maybe we can help
But I am pretty sure it is your CLASSPATH that is making your admin server fail |
|
| Back to top |
|
|
| nMQWF |
| Posted: Sun Oct 02, 2005 10:59 pm Post subject: Same problem |
|
|
Apprentice
Joined: 02 Oct 2005
Posts: 27
|
I have same problem on my machine.
Authentication.jar is the jar having the Authentication class.
Classpath : D:\workspaceGDC\DCAWF\Authentication.jar;........
Path:
d:\JRE\jre\bin;............
Error:
fmcerr.log
Error location = File=e:\v350\src\fmcaauth.cxx, Line=154, Function=FmcAuthenticationExit::Init
Error data =
Exception Class : FmcExitException
Error ID : A2
Error Description :
No Java-Authentication Exit available: could not access authentication method.
fmcsys.log
10/3/2005 11:39:08 AM FMC31050E An error has occurred which has terminated processing.
10/3/2005 11:39:08 AM
Exception Class : FmcExitException
Error ID : A2
Error Description :
No Java-Authentication Exit available: could not access authentication method.
Can someone help. Its urgent.
Thanks in Advance |
|
| Back to top |
|
|
| supreeth |
| Posted: Mon Oct 03, 2005 1:59 am Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi,
try out the following things.
1> Make sure you are using the correct version of jre. Authentication exit doesnt work with java versions prior to, i think 1.3.1 (service level 4).
2> Make sure you have the following things in the classpath
c:\WebSphere MQ Workflow\smp\java\authexit\fmcaexit.jar;c:\WebSphere MQ Workflow\smp\java\authexit and also the workflow jar files (fmcojagt.jar and fmcojapi.jar)
c:\WebSphere MQ Workflow\smp\java\authexit is very important. The root directory of ur relative path inside the jar file (com/ ...) should be there in the classpath
3> Make sure the jre bin and jre bin/ classic are there in the path
Set the classpath and path variable as system variables so that the values would be present in every window that is subsequently opened.
4> Restart the windows machine. Again, this is important as the classpath settings wont take effect until windows machine is restarted. this is strange but true.
5> Start the workflow service from the service menu. Its important to start the workflow servers as windows service and make its start type as "automatic"
6> Also workflow servers cannot be brought up from fmcautil. mike told he tried starting it from fmcautil
| Quote: |
| I tried starting the server from command prompt using fmcautil. |
fmcautil is jus the admin utility to administer the servers and the log files after the admin server is up.
Now, i guess the service should come up without any issues. Do reply back if u continue to face issues.
Thanks and Regards,
Supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Oct 03, 2005 6:10 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Supreeth:
I am currently experiencing the same issue on Windows XP with MQWF v3.6 and I can run the admin server as long as I run it from the command line.
fmcamain -c -y<cfg>
Try this and it should work if you are having the same issue as I am
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| supreeth |
| Posted: Mon Oct 03, 2005 7:50 am Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi John,
Incidentally,I have a similar setup as yours, i mean Windows xp (SP2) and MQWF 3.6. I am able to start the workflow servers as windows service and as well as through command prompt.
As i have mentioned in my previous mail, its a bit strange but we need to restart the windows machine for the classpath settings to get reflected in the windows service.
Sorry if i am being redundant but i would like to share what i have done as i have a working configuration.
1> Set (append) the classpath variable with values pointing to the exit jar file and the root directory from where you hav built the exit jar file as system variable (visible to all subsequently opened command prompts).
For eg: i have a directory structure of c:\com\ibm\workflow\java\exit for the exit, i shal put "c:\ and c:\fmcaexit.jar" in the classpath to accomodate the authentication exit
Putting c:\ in the classpath is essential as the file structure in the jar is relative to this path (root).
2> Path variable pointing to the correct jre bin and jre bin/classic
3> Restart the windows machine
It would not be a bad idea to switch on the trace to a level, say 3, if the servers fail to come up even now.
Hope this helps.
Thanks and Regards,
Supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
|
|
