The product is available Linux, Mac OS and Windows (64 bits) platforms.

Axional DBStudio requires Java JDK 1.8 available in your computer. If you don't have it already installed, you can download and install Java from https://www.java.com/download/.

Axional DBStudio product is distributed in a multi platform JAR (artifact) named:

axional-server-dbstudio-[VERSION]-all.jar

To install, simply copy the jar file to your system into an appropriate directory.

From operating system console run java command:

• MacOS:
  Copy

  $ java -XstartOnFirstThread -jar axional-server-dbstudio-[VERSION]-all.jar [--server] [--port num] [--swt] [--api]

• Linux:
  Copy

  $ java -jar axional-server-dbstudio-[VERSION]-all.jar  [--server] [--port num]  [--swt] [--api]

• Windows:
  Copy

  C: java -jar axional-server-dbstudio-[VERSION]-all.jar [--server] [--port num]  [--swt] [--api]

By default, with no arguments, the SWT application is started and the http server is disabled.

The following options are available:

• --server: Starts only the web server. The SWT app is not started.
• --port num : Specify a port number to be used by the web server.
• --swt: Forces SWT app to be started. This option only makes sense when used in conjuction with --server
• --api: Enables REST api web service (requires --server mode).

Contact with your provider to obtain a PGP license token.

Axional DBStudio includes a left pane with connection groups and instances and a right pane with related information.

Under the left pane you can setup the tree of groups and it's database servers. A sample structure can be as follows.

Loading...

digraph g { graph [fontsize=10 fontname="Verdana" compound=true]; node [shape=record fontsize=10 fontname="Verdana"]; edge [color=gray]; overlap=scale; # (try to) stretch everything if edges overlap splines=ortho; root [label="root node", fillcolor=blue, fontcolor=white, style="rounded,filled", shape=invhouse]; subgraph cluster_test { label = "Test"; test2 test1 } subgraph cluster_production { label = "Production"; CRM HR ER } root -> test1 root -> test2 root -> CRM root -> HR root -> ER }

In first run, you'll get a blank "unnamed" root node without any connection group or server connection. To create a new connection group, click right mouse button over root "unnamed" node and choose "Create new group" option:

Enter connection group name and press OK to create a new connection group. You can create as many connection groups as you require, to identify or categorize your instances. E.g. Production servers, Development servers, etc.

To create an instance connection definition in a connection group, right click over a group and choose "Create server" option on the popup menu.

You'll get a server form definition to enter data for your server connection:

When pressing OK button, server will be added to the servers group and if all data is properlly entered you'll get a server node to access to instance management.

You can refresh the catalog metadata if a connection is defined and you are connected. If other users have modified the metadata, you can see the latest changes.

Procedure

To refresh the catalog metadata for a database connection:

• In the Data Source Explorer, right-click on the database connection that you want to refresh.
• Select Refresh Objects Tree.

You can protect access to Axional DBStudio by requesting a user and password to run application

Select the root node (by default "unnamed") and click right button to open popup menu. Choose properties option and you'll get the root node configuration form.

This form allows to change the root node name and to introduce a user and password to protect application access. Leave user and password blank if you don't require pasword access protection.

It usually comes down to the issue that the Informix server is listening on a different network interface. In many cases the host name can route to an IP which is not the interface on which Informix is running as well, so when testing it’s best to use IP addresses when you are doing the local machine so you know what you are trying to connect to.

If you have the external IP for the windows machine and have not tried it I recommend trying that (even if it is local). You can also run `netstat -aon` and match it with the oninit process to see what IP/port combo it is listening on. It might be something surprising or different from the other Windows machine you said was connecting fine.

Dbaccess never helps you resolve connectivity problems unless you manually connect with ip + port as dbaccess defaults to shared memory connections.

Currently there is no debugging mechanism for showing the interface that JDBC is trying to connect to. This is an interesting case that really only shows up on Windows and typically once one knows which IP to connect to or change the server to listen on all adaptors with *HOSTNAME in the sqlhosts (adding the asterisk) then the problem goes away.