FAQs

ShipRush Server - Frequently Asked Questions

General FAQs

I am looking for OmniRush for parcel shipping. Where is it?
ShipRush Server is the parcel shipping part of the OmniRush Family. In 2004 OmniRush was rebranded into discrete brands: FaxRush, EmailRush, CashRush, PrintRush and ShipRush Server.

What's the difference between ShipRush for FedEx, ShipRush for UPS Basic, ShipRush for UPS Pro, ShipRush Server, and ShipRush SDK?
View the ShipRush Family Competetive Matrix.

How does ShipRush Server work?
ShipRush Server is a database-driven system. Typically, you create two new tables in your database: JOBS and HISTORY. The JOBS table has a foreign key off to a table where the recipient address information is stored. When you want to ship, your code
inserts a record into the JOBS table. ShipRush Server processes the shipment, and posts the results (tracking #, cost, etc.) to the HISTORY table (and deletes the record in JOBS).

ShipRush Server includes a simple 4-table sample database that is very easy to understand.

What are the stored procedures for?
When used with Microsoft SQL Server and Oracle systems, ShipRush Server requires that a kit of 10 simple stored procedures exist in the database. ShipRush Server is completely schema-independent. These sprocs simply need to give and take the required parameters.

The sprocs use simple SELECT / UPDATE / INSERT / DELETE syntax. They can be understood by anyone with a basic knowledge of SQL. You can either adapt these sprocs to your structures, or use the sample structures in your database.

When running in pass-through-SQL mode, there are no stored procedures. Instead, there are 10 SQL scripts that you modify to match your database schema (or use the sample schema).

Pass through SQL should work against most all SQL type databases that have an ADO driver for Windows. Known integrations include MySQL, Pervasive, and Postgress.