Business to business integration software as a service

A non-transitory computer-readable storage medium having stored thereon computer-executable instructions for performing a method of providing business to business integration software as a service, the method comprising:

• providing a hub environment, the hub environment comprising a hub web service access point, a hub transaction router, a hub messaging system, a hub adapter container, a hub adapter generator, a hub enterprise information system (EIS) connector, and a hub management console;
• generating a plurality of spoke environments, at least one of the plurality of spoke environments comprising:
• a spoke web service access point;
• a spoke messaging system;
• an adapter container comprising:
• (i) one or more adapters configured to map data elements of one or more transaction types used for interactions between at least one EIS local to a first computer and at least one EIS local to a second computer to data fields of the at least one EIS local to the second computer, wherein the transaction types comprise one or more selected from the group consisting of purchase order, purchase order acknowledgement, invoice, and advance ship notice;
• and
• (ii) a pre-filter and a post filter for at least one of the one or more adapters;
• a spoke EIS connector;
• a spoke configuration manager configured to define new transaction types, in communication with the hub environment, processing web service requests therefrom, and deploy new adapters into the adapter container, wherein the spoke configuration manager configures the pre-filter and the post filter;
• and
• a spoke management server;
• and
• deploying the plurality of spoke environments to one or more remote computers, at least one of the plurality of spoke environments deployed to the second computer for installation on the second computer;
• exerting control over the at least one spoke environment deployed to the second computer via the hub environment, the exerting comprising, after deploying the at least one spoke environment deployed to the second computer:
• defining one or more new transactions types via the hub management console;
• generating, via the hub adapter generator, one or more new adapters configured to map data elements of the one or more new transaction types to data fields of at least one EIS local to the second computer;
• deploying the one or more new adapters and the one or more new transaction types from the hub environment to the at least one spoke environment deployed to the second computer;
• and
• deploying the one or more new adapters into the adapter containers of the at least one spoke environment deployed to the second computer via the at least one spoke configuration manager of the at least one spoke environment deployed to the second computer.