processmaker : connect to database - database

according to the title, i want to connect the process maker to the database.
i use MySql as an engine, the server is localhost, and the port is 3306. after submit the configuration, then the processmaker doing 4 steps to test the connection. i already passed the first 2 step, but the 3 and 4 step are failed.
the processmaker say :
MySql connection refused!
i follow the instruction from http://wiki.processmaker.com/index.php/Database_Connections
but it still doesn't work.
thanks for your answer

Did you verify that your information is the correct one???
Check your mysql Username and password, and try using 127.0.0.1 as server

When you installed ProcessMaker, which database did you use as a default one?, I've asked you this beacuse ProcessMaker comes with Apache and Mysql by default so maybe this step is unuseful to do.
Regards,
processmaker

make sure you are using correct version of mysql supported by processmaker.

Related

Connecting Apache Superset to an external database

I am running apache superset on docker, and I have been trying to connect to an external database(Postgres) using the example link on SQLAlchemy Docs for connecting to a Postgres database (postgresql://scott:tiger#localhost/mydatabase // postgresql://username:password#localhost:5433/postgres). However, I have been getting the following error: Connection failed, please check your connection settings. Could someone please help me with this.
Are you sure that your postgres is on the same network (localhost)? It seems for external database, that it would likely be on another network (and therefore you would use IP address)?
If these are the docs you are looking at --> https://docs.sqlalchemy.org/en/12/core/engines.html#database-urls
Then you might want to think in terms of 'host', meaning then an IP(v4) address and/or DNS.
As it was recommended you may need to whitelist your Superset IP address in pg_hba.conf.
You may also need to check if you have the right driver installed in the docker instance that you are running superset.

MediaWiki installation issue - port problems

I am trying to install MediaWiki version 1.31 localy and I have run into some issues that I cant get past by. Mainly when I input datatabe connection (I am trying to connect to PostgreSQL database) information it returns this error.
Thing is the port I am trying to connect is 5433 not 5432, also the names "template1" and "postgres" are not included in my input trough the dialogue screen - I dont know where they came from. "test1" is the name of the database I am trying to connect to.
Any help or advice how to get trough this error would be greatly appreciated. Thank you.
That the port you specify is not used while setting up the database schema in the first place is a long-standing known bug. One workaround is to run your database on the default port until you have wiki set up, then change it back to the port you want.
In order to create a new database, you need to connect to an existing database in the same cluster. 'template1' and 'postgres' are pre-existing databases (usually created at the time the cluster was created) commonly used to connect to in order to create a new database. These names are "well-known", you don't need to specify them.

Installing database when create a clone of website in local server

G'day, I am trying to make a clone of the WordPress website into my local server. I installed the Duplicator plugin and generated a archive file of the website and the installer.php. Then after ran the installer.php from http://localhost:8888/untitledfolder/installer.php.
In the step 2 (Install Database) there is an error which is a connection failure. I already created a database named 'livewebsite' beforehand. It's likewise the below image.
Any help would be really appreciated though I am new to WordPress trying to learn from the scratch. No down votes for the question please. Thank you! :)
I got the issue. That was my username and password. Username & password should be default data which is root and 123 for my settings. Thank you!
You should change MySQL port (the right input with localhost) from 8888 to 3306. That's the real port of MySQL server.
After change and retry, you can see the Host: Fail will become Host: Success with green flag I think. If Database still have a red fail flag, please edit your database username and password. It's not your WordPress account.

Setup SQL Server JDBC Connection Pool and Resource on Tomcat 7

Firstly let me start off by saying I've been Googling for quite some time now and I can't find a straight forward answer to this. Either my Google-Fu is terrible or there really isn't a clear and simple way of doing this. Even on the official site I get pages and pages of jargon.
I'm used to Glassfish and am quite spoiled when it comes to connection pool setup especially with the Glassfish admin console. What I'm looking for is just a simple step by step, e.g. 'Go to this file, add this xml tag', paste your JDBC driver in that folder, done'. But I can't find something like that.
What I have is
The Server IP Address the Database is on
The database name
The username
Password
and JDBC Driver .jar file
It would greatly be appreciated if someone can clear things up for me a bit. Thanks!
Here is the document for setup tomcat connection pool using DBCP

Creating SQL Server database without the /MSSQLSERVER in the connection string?

I found this pretty weird thing when I first installed SQL Server 2008, for some reason there are two things that I want to get rid of and I can't:
If my computer name is, say, ABC, then I always have to connect to ABC/MSSQLSERVER for the server name when I log in from the SQL Server client, instead of using just using ABC, may I know how I can do that?
How can I default the DB so that if I have multiple DB on the server (System DB + my real DB), I can always default to use my real DB without saying "Use MyRealDB" every time?
Thanks a lot!
Regards,
Anyi
1) When installing, you picked a named instance.
2) In user admin, you can specify the default database per user.
What's happened here is that your SQL Server is installed as a named instance. To remedy this, you'll have to remove and reinstall SQL Server.

Resources