Relational Junction will work on any web application server, including WebLogic, if the app server supports Java 1.8. Nearly all of our customers use Tomcat, since it provides all the services required for the web administration without any licensing costs. Relational Junction is primarily a batch system. You can fire off jobs in the web user interface, but stopping Tomcat does not kill the jobs. It is far better to have  a dedicated server for Relational Junction, because of the batch orientation, than use a web application server with many other transactional applications running.

Yes. The client is just a compatible web browser. The server component does need to be installed, and requires Java and Tomcat.

Yes, all browsers that support CSS3 and HTML5 are supported. It can be configured for SSL (port 443) if you have an SSL cert, but typically customers who implement on-premise use port 8080.

Relational Junction is a Java application, and is therefore completely cross-platform. Deployment options include

  • On-Premise servers and personal computers, including Windows, Mac, and UNIX
  • Amazon AWS
  • Microsoft Cloud
  • Any Cloud computing environment where you have access to install Java and Tomcat

 

Yes, Windows Scheduler or UNIX cron or any other job scheduler is normally used to initiate replication or integration jobs. The web client is used to set up and test the job, but is not for normal production job scheduling. The command line interface is very easy to run from any scheduling system.