Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
10 replies
Subscribers
7 subscribers
Views
3292 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Been following the installation guide line by line. Created the two databases in
neron
over 9 years ago
Been following the installation guide line by line. Created the two databases in MySql using "CREATE DATABASE appian_primary" and "CREATE DATABASE appian_businessdata" commands (still pretty new to MySql and all this). I left everything in the appian-mysql-ds.xml.<ENVIRONMENT> file default since the names followed the ones in the example.
Getting some "could not create keystoreconfig" and "could not find datasource" errors when running standalone.bat
application-server.log
OriginalPostID-190088
OriginalPostID-190088
Discussion posts and replies are publicly visible
0
Khalil Ben Naceur
Appian Employee
over 9 years ago
Hi,
The relevant error here is:
Could not find datasource: jdbc/AppianPrimaryDS
javax.naming.NameNotFoundException: jdbc/AppianPrimaryDS
Please review the following Knowledge Base article which references this issue:
forum.appian.com/.../kb-1009.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
neron
over 9 years ago
This is what I had for the datasource names in both files. Can you verify that this is correct?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Khalil Ben Naceur
Appian Employee
over 9 years ago
If appian_primary and appian_business are the names of your MySQL databases and if your databases are hosted in the same server as your Appian/Jboss install, then yes.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
neron
over 9 years ago
These are the Operating System requirements:
forum.appian.com/.../System_Requirements.html
I'm currently using Windows 10 Home edition. Could this be the issue?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Khalil Ben Naceur
Appian Employee
over 9 years ago
You are correct in mentioning that Windows 10 Home edition is not supported. This may lead to issues down the line but this does not seem to be related to the OS version.
Can you please attach a screenshot of the DS part of standalone.xml? Please hide your username and password.
Ultimately, we strongly recommend switching to an OS supported by Appian.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
neron
over 9 years ago
This is the pic of the standalone.xml file. I kept all of the naming standard like in the example and only updated the two lines mentioned by adding in the username and password.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
neron
over 9 years ago
I checked the user on the MySql side. The user account has been given full rights to the appian_primary and appian_businessdata schemas (all check boxes checked).
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Khalil Ben Naceur
Appian Employee
over 9 years ago
Have all the changes been deployed to the environment via the configure script?
Additionally, were you able to follow the steps of the knowledge base article, specifically steps 5 and 6?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
neron
over 9 years ago
I redeployed to both Appian and Jboss using the configure.bat
In steps 5 and 6, I did find a appian-mysql-ds.xml.undeployed which I renamed to appian-mysql-ds.xml.dodeploy and I found a suite.ear.failed file which I renamed to suite.ear.dodeploy.
These files will re-appear after another unsuccessful run of standalone.bat
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
neron
over 9 years ago
FYI, it's been able to access the dbs and create the tables each time I've run it. It just fails to deploy the /suite web service.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel