Description: TIBCO ActiveMatrix BPM (AMX BPM) has introduced installing Developer server profile from version 3.1. When the Developer server is created, AMX BPM uses PostgreSQL database. The database instance is named as "bpm" and username is "bpmuser" by default.
When a connection is attempted from Oracle SQL Developer to connect to PostgreSQL, the connection is successful only for the Postgres Admin
user (postgres). The SQL developer could not identify or connect to a BPM database
instance in the PostgreSQL db. Even if a connection is obtained by specifying the instance name along with hostname in the URL, the tables are not listed.
Symptoms: Upon trying to connect to the "bpm" schema in PostgreSQL, the SQL Developer server throws, "Failure -FATAL: database "bpm" does not exist" error
Cause: Oracle SQL Developer does not officially support PostgreSQL. The connection to Postgres DB through Oracle SQL Developer is successful only for the Postgres admin
user. SQL Developer could not identify or connect to the BPM database
instance in the Postgres db. The issue is because SQL Developer expects the database instance name
and the user name to be same. In the Developer installation profile, the
username for the BPM user (bpmuser) is different from the database instance name (bpm) that
is created.
Issue/Introduction
Connecting to PostgreSQL DB through Oracle SQL Developer for TIBCO ActiveMatrix BPM Developer environment.
Resolution
The resolution is to use a different database client like pgAdmin to connect to Postgres DB schema for the Developer server installation