Yes. Relational Junction for Salesforce allows you to create separate configurations to subset the objects and to point to different databases. You specific which configuration you want to use for each job, giving you total flexibility to mix and match.
Yes, you can subset the Salesforce objects to include any specific objects. You can also limit replication to Standard, Custom, History, Chatter, Share, or Tag objects.
Yes, both full or incremental replication are supported, but you will typically run incremental. This is much faster, since only changed and new records are copied.
Yes, there are logs that show progress. There is no “thermometer” widget, but the logs are much more informative.
Jobs can be scheduled with Windows Scheduler, UNIX cron, Control-M or any other job scheduler. Some customers trigger jobs from other ETL products. All it requires is a process that can invoke Relational Junction‘s command-line interface.
A user can initiate a job by entering a command such as “RJ4Salesforce -config production -getGlobal”.
A user can initiate a job through the web user interface.
There is a Real-Time mode that captures OutBound Messages that you configure in Salesforce to trigger replication of the entire record.
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.
Yes. You can set what percentage of your daily API limit the product should use before stopping replication to ensure that you don’t exceed the limit and other API applications are not impacted.
None. We use the API server, not the UI server. Salesforce is a multi-tenant environment, and each API server is shared with thousands of their customers, so the net impact of replication on overall system load and performance is negligible.
Zero footprint. Nothing is installed in Salesforce.