DapTrial 10.3. MWS Install with error db.type, db.url, db.username and db.password parameters...

Installation of DapTrial 10.3 under Windows Server 2016 failed at MWS create instance phase with
ERROR: db.type, db.url, db.username and db.password parameters are required when creating an instance.
Please, advise how to resolve this case.

Thanks and regards,
Vladimir

The setup.properties file is:

IboInstallDir=C:\SoftwareAG
#— Database access parameters —

DBCFG_URL=jdbc:mysql://localhost:3306/dbname

DBCFG_URL=jdbc:wm:sqlserver://localhost:1433;databaseName=WEBMDB;MaxPooledStatements=100
DBCFG_NAME=WEBMDB

DBCFG_TABLESPACE_DIR=…

Type of RDBMS: must be one of “SQL Server”, “Oracle”, “DB2”

DBCFG_DRIVER=SQL Server
DBCFG_ADMIN_USERNAME=sa
DBCFG_ADMIN_PASSWORD=Password4sa!
DBCFG_USERNAME=ibo_bam
DBCFG_PASSWORD=SoftwareAG1!
#— MySQL database access parameters

MYSQLCFG_HOST=127.0.0.1
MYSQLCFG_PORT=3306
MYSQLCFG_USERNAME=root
MYSQLCFG_PASSWORD=manage

MYSQLCFG_CONNECTOR=c:\DapTrial-10.3\mysql-connector-java-8.0.14.jar

The c:\SoftwareAG\install\logs\installLog.txt contains

10:10:49 info PortalServerInstances.installInit() this=com.webmethods.portal.install.server.PortalServerInstances@7593ea79, thread=1
10:10:49 info PortalServerInstances.installInit(): installWorkUnits 1
10:10:49 info PortalServerInstances.installExecute() installWorkUnits=1, this = com.webmethods.portal.install.server.PortalServerInstances@7593ea79, thread = 1
10:10:49 info PortalServerInstances.installExecute(): createInstance = true
10:10:49 info PortalServerInstances.installExecute(): instanceName = default
10:10:49 info PortalUtils.createMWSInstance()
10:10:49 info PortalUtils.executeCommand(): C:\SoftwareAG\MWS\bin\mws.bat …
10:10:49 info PortalUtils.executeCommand(): -c …
10:10:49 info PortalUtils.executeCommand(): new …
10:10:49 info PortalUtils.executeCommand(): -Ddb.password=****** …
10:10:49 info PortalUtils.executeCommand(): -Dserver.name=default …
10:10:49 info PortalUtils.executeCommand(): -Ddb.url=jdbc:wm:sqlserver://localhost:1433;databaseName=WEBMDB;MaxPooledStatements=100 …
10:10:49 info PortalUtils.executeCommand(): -Ddb.type=ms …
10:10:49 info PortalUtils.executeCommand(): -Dnode.name=mosps01.eur.ad.sag-node5665 …
10:10:49 info PortalUtils.executeCommand(): -Ddb.username=ibo_bam …
10:10:49 info PortalUtils.executeCommand(): -Dhttp.port=8585 …
10:10:49 info PortalUtils.executeCommand(): -Dinstall.service=false …
10:10:51 info executeCommand(): output:
JAVA_HOME: C:\SoftwareAG\jvm\jvm
MWS_HOME: C:\SoftwareAG\MWS
WM_HOME: C:\SoftwareAG
Creating new server instance. Please wait…
Buildfile: C:\SoftwareAG\MWS\server\deploy.xml
ERROR: db.type, db.url, db.username and db.password parameters are required when creating an instance

10:10:51 info PortalUtils.executeCommand() exit code: 3
10:10:51 error APP_ERROR> MWS.E.0002: Error occured while creating My webMethods Server server instance “default”
10:10:51 internal java.lang.Exception: Process execution failed: exitCode=3, error=
at com.webmethods.portal.install.server.PortalUtils.executeCommand(PortalUtils.java:197)
at com.webmethods.portal.install.server.PortalUtils.createMWSInstance(PortalUtils.java:104)
at com.webmethods.portal.install.server.PortalServerInstances.installExecute(PortalServerInstances.java:75)
at com.wm.distman.install.DistManConsole.displayProgressGroupPanelConsole(DistManConsole.java:573)
at com.wm.distman.install.DistManConsole.nextInstallerPanel(DistManConsole.java:218)
at com.wm.distman.install.DistManConsole.start(DistManConsole.java:23)
at com.wm.distman.install.DistManMain.launch(DistManMain.java:110)
at com.wm.distman.install.DistManInstallMain.launch(DistManInstallMain.java:60)
at com.wm.distman.install.DistManInstallMain.main(DistManInstallMain.java:70)

Hi Vladimir ,

The problem is in the parameters that you have provided in the properties file.

ERROR: db.type, db.url, db.username and db.password parameters are required when creating an instance

Please use the below steps to create MWS instance.

  1. Goto /MWS/bin
  2. ./mws.bat new -Dserver.name= -Dhttp.port=8585 -Ddb.type= -Ddb.url=’’ -Ddb.username= -Ddb.password=

Earlier you haven’t used these parameters while creating the instance- [db.type, db.url, db.username and db.password]

With Regards,
Nayan

Hi Nayan,

Your advise is a valid one when I’m doing standalone MWS install.
In my case, I’m running DapTrial-10.3 package and start installation as:

grexec DapTrial -install

this package requires to setup a config file setup.properties, where I input all requested parameters. You could see it in my first mail.
Moreover it looks that these parameters are taken by groovy script for mws.bat run, as it’s logged in the install.log (again, see my first mail, line started with “PortalUtils.executeCommand()” ), but somehow not used when mws.bat command srting is generated…

Thanks and regards,
Vladimir

Hi Vladimir Silin ,

DAP instalation is bit different from normal installation of WebM products.
DAP installation step creates database during installation of products itself.It is must have to have working Mysql db connection with proper credential for it. So please dont skip database input text box during installation to avoid this failure.

Thanks & Regards,
Manoj

Hi Manoj,
MySQL is installed and database for AgileApps is created. Do you mean that MWS, IS, Optimize and other components must be installed in MySQL as well? The guide tells that “The webMethods DAP trial package for 10.3 is tested with only Microsoft SQL Server.”
BTW, I did not see input text box during execution of grexec DapTrial -install.

Thanks and regards,
Vladimir

with DAP, Only AgileAPP will use Mysql but ther servers like MWS, IS, optimize will still need SQLServer as suggested in guide http://techcommunity.softwareag.com/web/guest/pwiki/-/wiki/Main/Guide+to+Downloading+and+Installing+the+webMethods+BPMS+Free+Trial+Version.

Since it is a free trial downloder, you will not see any popup for mysql credential as it is alredy provided in .property file.

The real issue here is a known issue which is due to database password contains exclamation character(!) and this is causing the mws instance to not get created. This will be fixed soon.

So as a workaround, you can change the password “SoftwareAG1!” to something which exludes exclamation character(!).

Hope this will resolve your issue temporarily

Thanks & Regards,
Manoj

Hi Manoj ,
After changing password by eliminating exclamation sign the install phase executed without any errors.
Many thanks for your advice,
Vladimir

you’re welcome.