In an attempt to get a better understanding of Sage ERP X3 Web Services, inlcuding X3 Web Channels and X3 Java Bridge Library, I found some useful information in the Sage ERP X3 Configurator, basically the price list. I thought I would share my findings related to the Sage ERP X3 Web Services Channels ("WS Channels") and Java Bridge Library as I am sure there are others in the same category as me.
After obtaining this initial information I mentioned above I had some further questions that required research to gain a better understanding of how these components are made available to customers and sizing them for an implementation. I reached out to Sage, and a few of my colleagues and researched some documents I have obtained over the past few years. In this post I will cover the WS Channels.
1. It appears as though a Web Service channel is good for about 20 users. This really depends on the actual amount of activity per user of course and results may vary. The 20 users is more of a guideline.
a. So if I have 80 users hitting the Web Services I would most likely want to purchase 2 additional Web Service channels since I already had 2 Web Service channels with my initial purchase. Again you need to realize it would be depend on activity and end user expectations.
- Each Web Services Channel handles approximately 20 simultaneous inquiries, so 4 channels would be used to accommodate 80 users with acceptable response times. Fewer channels would slow down the response time.
2. It looks like a customer gets 2 Web Service channels with their purchase of Sage ERP X3. However you must select the Web Service channel on the Configurator if you want the 2 free WS Channels.
a. Do they need to then purchase internal or external users in addition to these channels?
- External Web Services Users are currently on the Configurator as of Sage ERP X3 v6.5 however they are being removed, which allows unlimited user access using external web services. An updated Configurator will be published shortly.
- If Internal Web Services Users are needed, they would be purchased separately.
b. If so, how do we know how to determine when they need these User licenses?
- Internal Web Services Users are defined as: "can access the system indirectly through internal Web Services channels (e.g. customer inquiry through a connected intranet service)".
3. If I purchase the ISV Connector, which is an option on the Sage ERP X3 Configurator…
a. Do I use any of my free 2 WS channels or does this ISV Connector come with a channel?
- Sage ERP X3 ISV Connectors do not include Sage ERP X3 Web Services Channels.
- If a customer needs more than the 2 Channels that are included with the product, they would be purchased separately.
- A separate WS Channel is required for each Web Service (e.g., two separate Web Services cannot share one Channel).
b. Do I need to purchase those User licenses as well?
- If needed, Internal Web Services Users would be purchased.
- External Web Services Users are being removed as stated above.
The following information is from the Sage ERP X3 Configurator and provided here just for additional clarity and points of reference related to Web Services Channels, Web Services Users, Java Bridge and ISV Connectors.
Web Services Channels
Web Services Channels are necessary for external applications to utilize resources of the Sage ERP X3 system. This option allows extending the 2 Web Services Channels provided by default with the Software License. At least one Channel is required per Web service application. The number of Channels required for a given application depends on the level of performance that is expected (number of simultaneous inquiries and volume of data to process at each connection). On average, one channel is capable of processing 20 simultaneous inquiries with an acceptable response time.
From the version 6.5, the 2 Web Services Channels free delivered will be provided only on demand, in order to enhance the deliveries traceability and to avoid hidden sale of a runtime license for database. Demand must be mentioned on the Configurator.
Java Bridge Connections
Java Bridge Connections are necessary for Sage ERP X3 to utilize resources of external Web services (e.g. access Sage Connected Services such as Sage Exchange and Sage Tax Management by Avalara). This option allows extending the 2 Java Bridge Connections provided by default with the Software License.
ISV Connectors are predefined Web Services that facilitate the integration of Sage ERP X3 with third-party solutions by offering a standard access to the Sage ERP X3 objects and processes commonly used by certain types of applications. Standard connectors are available to integrate with the following ISV applications: Product Lifecycle Management, Electronic Document Management, Manufacturing Planning and Scheduling, Manufacturing Forecasting, Plant Maintenance and Manufacturing Execution Systems.
Web Service Users
- Internal Web Service Users can access the system indirectly through internal Web Services channels (e.g. customer inquiry through a connected intranet service).
External Web Service Users can access the system indirectly through external applications utilizing a Sage ERP X3 Web Services channel (e.g. stock inquiry through a connected e-commerce application)
NOTE: It is my current understanding as of the time of this blog post that External Web Service Users are being removed from the Sage ERP X3 Configurator and will not require separate purchase. This is of course subject to change at a future point in time by the Software Publisher.
I hope you found this useful. I want to thank Gia Lane from RKL eSolutions and Kevin Babb from Sage for their assistance in compiling some of this information.