| Author |
Message
|
| DragonFist |
 Posted: Thu Nov 20, 2003 7:49 pm Post subject: Workflow configuration |
 |
|
Acolyte
Joined: 11 Nov 2003
Posts: 52
|
Hi all
I am having problems configuring my workflow. I got this following error while final configuration step...
-------------------------------------------------------------------------------------
11/20/2003 7:28:04 PM FMC33136I Generating database layout.
11/20/2003 7:28:04 PM FMC33153W The managed by value for tablespaces belonging to group INDEX is not customizable.
11/20/2003 7:28:05 PM FMC33110I The database manager is already active.
11/20/2003 7:28:06 PM FMC33115I Creating the database - FMCDB
11/20/2003 7:28:06 PM FMC33116I Please wait... This may take a while.
11/20/2003 7:30:12 PM FMC33117I Database FMCDB has been created.
11/20/2003 7:30:12 PM FMC33120I Updating the database configuration.
11/20/2003 7:30:12 PM FMC33974W Database command 'sqlfudb' was not performed due to the following error : 'SQL5099N The path "C:\Program Files\IBM WebSphere MQ Workflow\rt_db\DB2\FMCD" indicated by the database configuration parameter "NEWLOGPATH" is not valid, reason code "4"'.
11/20/2003 7:30:12 PM FMC33975I Make sure to execute the above command prior to starting WebSphere MQ Workflow servers.
11/20/2003 7:30:21 PM FMC33132I Creating tablespaces.
11/20/2003 7:30:22 PM FMC33148E DB2 CLI call 'SQLExecDirect(CREATE TABLESPACE ACTWI MANAGED BY SYSTEM USING ('c:\program files\ibm websphere mq workflow\rt_db\db2\fmcdb\actwi'))' ended with error: '[IBM][CLI Driver][DB2/NT] SQL0298N Bad container path'.
11/20/2003 7:31:16 PM FMC33136I Generating database layout.
11/20/2003 7:31:16 PM FMC33153W The managed by value for tablespaces belonging to group INDEX is not customizable.
11/20/2003 7:31:16 PM FMC33110I The database manager is already active.
11/20/2003 7:31:16 PM FMC33115I Creating the database - FMCDB
11/20/2003 7:31:16 PM FMC33116I Please wait... This may take a while.
11/20/2003 7:31:17 PM FMC33146E DB2 API call 'sqlecrea' ended with error: 'SQL1005N The database alias "FMCDB" already exists in either the local database directory or system database directory'.
-------------------------------------------------------------------------------------
can anybody explain what the problem is .. and how to solve it...
Anyhelp would be appreciated..
Thanks
_________________
DragonFist |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Nov 20, 2003 8:43 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I am not a DB2 guy or a windows guy so I can't really tell you how to get rid of the registry entry. If you know how to do that then get rid og the registry key for the FMCDB database.
You change the name of the runtime database and you should be able to create a new configuration. |
|
| Back to top |
|
|
| devin |
| Posted: Fri Nov 21, 2003 6:15 am Post subject: |
|
|
Voyager
Joined: 27 Oct 2003
Posts: 82
|
Did you have workflow configured on that machine before?
It could be that there are some remains left of the previous configuration which is creating problems. |
|
| Back to top |
|
|
| DragonFist |
| Posted: Fri Nov 21, 2003 1:19 pm Post subject: webclient problems |
|
|
Acolyte
Joined: 11 Nov 2003
Posts: 52
|
Hi all
thanks for the replies. Insteading dealing with the registries etc.. I simply reinstalled my XPPro and tried to install everything again. I am facing problems again during the configuration.. Here are the errors that showed up again...
-----------------------------------------------------------------------------------
11/21/2003 1:50:41 AM FMC33746I Creating the Web Client files ...
11/21/2003 1:50:45 AM FMC33938I Creating 'fmcohcli.war'
11/21/2003 1:50:45 AM FMC33687I c:\PROGRA~1\WEBSPH~1\DEPLOY~1\java\bin\jar cMf fmcohcli.war -C webpages\ .
11/21/2003 1:50:48 AM FMC33938I Creating 'fmcohcli.ear'
11/21/2003 1:50:48 AM FMC33687I c:\PROGRA~1\WEBSPH~1\DEPLOY~1\java\bin\jar cMf fmcohcli.ear fmcohcli.war META-INF fmcojagt.jar
11/21/2003 1:50:50 AM FMC33667I The creation of the Web Client completed sucessfully.
11/21/2003 1:50:50 AM FMC33737I Importing the Web client into WebSphere ...
11/21/2003 1:50:50 AM FMC33687I wsadmin.bat -c "$AdminApp install c:/PROGRA~1/IBMWEB~1/cfgs/fmc/WEBCLI~1/fmcohcli.ear { -appname MQWF_Web_Client_FMC -preCompileJSPs}" > "c:\program files\ibm websphere mq workflow\cfgs\fmc\log\wsadmin.log" 2>&1
11/21/2003 1:51:05 AM FMC33687I WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException
11/21/2003 1:51:05 AM FMC33687I WASX7213I: This scripting client is not connected to a server process; please refer to the log file C:\Program Files\WebSphere\DeploymentManager\logs\wsadmin.traceout for additional information.
11/21/2003 1:51:05 AM FMC33687I WASX7022E: Problem running command "$AdminApp install c:/PROGRA~1/IBMWEB~1/cfgs/fmc/WEBCLI~1/fmcohcli.ear { -appname MQWF_Web_Client_FMC -preCompileJSPs}" -- exception information: com.ibm.ws.scripting.ScriptingException: WASX7206W: The application management service is not running. Application management commands will not run.
11/21/2003 1:51:05 AM FMC33687I
11/21/2003 1:51:05 AM FMC33658E The configuration within the WebSphere Application Server ended with error: 'WASX7022E: Problem running command "$AdminApp install c:/PROGRA~1/IBMWEB~1/cfgs/fmc/WEBCLI~1/fmcohcli.ear { -appname MQWF_Web_Client_FMC -preCompileJSPs}" -- exception information: com.ibm.ws.scripting.ScriptingException: WASX7206W: The application management service is not running. Application management commands will not run.'
11/21/2003 1:51:59 AM FMC33006E The configuration failed! Log was written to 'c:\program files\ibm websphere mq workflow\cfgs\fmc\log\fmczkcfg.log'.
-------------------------------------------------------------------------------------
It successfully created all the runtime, buildtime databases and also the web client.. Only on the final configuration it failed.. i mean while uploading th webclient into websphere. Could this be because i might have given the wrong path for websphere while configuring... if anyone has faced this problem earlier or if someone knows the solution please help me..
Thanks in advance
_________________
DragonFist |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Nov 21, 2003 1:30 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Was your WAS running when you tried to create the configuration. If you know how to deploy an ear file into WAS then you could as well do that.
What version of WAS are you runnng. |
|
| Back to top |
|
|
| DragonFist |
| Posted: Fri Nov 21, 2003 1:50 pm Post subject: |
|
|
Acolyte
Joined: 11 Nov 2003
Posts: 52
|
WAS is not running while configuring the workflow as far as i know. I dont know how to deploy EAR files on WAS.. please provide me the instructions on this one.
I have WAS 5.0.
Thanks in Advance
_________________
DragonFist |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Nov 21, 2003 2:07 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You need to have WAS running if you wan to create a web client configuration and the config utility to install the web client on WAS.
| Quote: |
dont know how to deploy EAR files on WAS.. please provide me the instructions on this one.
|
Not me either.. sorry.
It would be a ood idea to start off afresh.
Delete the old configuration, say "YES" when the utility says it will delete the queue manager and database. Start off afresh.
If you still want to use the old configuration, create another configuration for web client (this time make sure your WAS is running) |
|
| Back to top |
|
|
| DragonFist |
| Posted: Fri Nov 21, 2003 3:09 pm Post subject: |
|
|
Acolyte
Joined: 11 Nov 2003
Posts: 52
|
Hi I started the WAS server before starting the configuration. But still it gave me the same error. I deleted the Fmcdb everything as you said so that i configure it with the default values. What it says is it could not start the wsadmin.bat and then gave all the errors. Also I want to make sure one more thing. My WAS is installed in C:\Program Files\webshpere\deployment manager. In workflow config when u give the websphere location i tried bothways giving C:\Program Files\webshpere\deployment manager and C:\Program Files\webshpere. It did not worked either way. Is it becos it could not reach the destination folder of wsadmin.bat to start it... as it says it is not an executable command on dos as per error in WF config. Also do i have to check the IBM Websphere 5.0 option or a diff one in WF config. I have J2sdk1.4.2 version on my system. Please clarify me on this one..
Thanks
_________________
DragonFist |
|
| Back to top |
|
|
| DragonFist |
| Posted: Fri Nov 21, 2003 3:35 pm Post subject: |
|
|
Acolyte
Joined: 11 Nov 2003
Posts: 52
|
Hi I started the WAS server before starting the configuration. But still it gave me the same error. I deleted the Fmcdb everything as you said so that i configure it with the default values. What it says is it could not start the wsadmin.bat and then gave all the errors. Also I want to make sure one more thing. My WAS is installed in C:\Program Files\webshpere\deployment manager. In workflow config when u give the websphere location i tried bothways giving C:\Program Files\webshpere\deployment manager and C:\Program Files\webshpere. It did not worked either way. Is it becos it could not reach the destination folder of wsadmin.bat to start it... as it says it is not an executable command on dos as per error in WF config. Also do i have to check the IBM Websphere 5.0 option or a diff one in WF config. I have J2sdk1.4.2 version on my system. Please clarify me on this one..
Thanks
_________________
DragonFist |
|
| Back to top |
|
|
|
|
