Resources and News
There is a new State of the API Briefing you can see at Scribd page Here
A large amount of Functional Sample code is soon to be released by Todd. And, a new API monitor endpoint is being defined, so you can watch your account sessions and invoked functions execute in real tine. Very handy for those getting their feet wet, and great for debug.
As always, if you have requested developer login credentials and have either stalled, need help, or an API walk through, please let us help you get bootstrapped. We are here to help make your EDI feature set more compelling and transparent with the best EDI Communications API and Network. Period.
Alan 412-353-9269 anytime,
The relationships of Mailboxes and Associated QIDs, subscription charges, routing, etc.
The ECGridOS API is focused on the mailbox. At the code level, your code, you can create mailboxes, users, interconnects, and send and receive data. From a routing standpoint, any QID’s you create belong to the mailbox you are logged into at time of instantiation. There are also API functions for assigning QIDs to exogenous mailboxes. ECGrid handles the QID field as a route inbound. Therefore, one can have a mailbox (each mailbox includes 2 QID’s) with many QID’s.
At a cost of $4.95 per additional QID, why wouldn’t everyone want to load up, and use the overloading of QID’s as logical mailboxes? Here are some answers:
1. You would need to write more code to handle the sorting, archiving, and general management of QID’s. ECGridOS has functions for managing the QID’s and their mapping to ECGrid IDs. However, as nice as that is, all of the network and administrative power comes from the mailbox API. But please be our guest to proceed with QID loading if that fits your style.
2. Cost savings is not enormous for production quantities of mailboxes, especially for SAAS and B2B hub platforms. A B2B Power Cloud might use ECGridOS for batches of 100’s or 1000’s of users and mailboxes. At the typical mailbox discount on these types of contracts and unlimited annual licenses, the code burden for QID management does not equal the lost convenience of session, user, and archiving functions that properly belong to the mailbox. Put another way: “Your QID’s are routes to your mailbox, as found in the ISA or UNB message segments. QID’s a are not discrete accounts. Mailboxes are accounts, QID’s belong top your mailbox, as do users.
3. In any case, with the ECGridOS API, you have the power to do as you wish, and you can test each methodology to prove my point that for multi-Tenant platforms, each account should have its own mailbox. A very brief review of the API will bear this out.
Recent News About Loren Data, ECGrid, ECGridOS, Upcoming Events and Tools + Partnerships
11/24/2009 Tradacoms EDI envelope format enters ECGrid / ECGridOS beta. API developers who are also servicing Tradacoms interchange segments should be happy.
The latest from Todd on 8/4/09
2009 is shaping up to be an incredible year for both Loren Data and the industry, perhaps we can be the ones that lead this country back to productivity, efficiency and out of this recession.
New ROUTING REQUESTS Procedures: (its an improvement, dudes, chill)
By the end of August we will have a new routing request process in place. You will have the choice of either using a new Web-Based UI or our ECGridOS API. In both cases, you will have immediate response to the status of your Routing Request, and 80% of the time it will be instantly confirmed. For those requests that require confirmation by the VAN or other assistance, they will be immediately escalated to NetOps for completion. The Web-Based UI will use the ECGridOS API on the back end, and source code will be published to assist developers in writing their own ECGridOS-aware applications. We will be providing several Webinars for training, which will be recorded for playback at any future date.
VAN SUMMIT II:
Sorry folks, there has been a last minute decision to cancel the VAN Summit and Keynote, due to lack of enrollment. Todd will be in LA to meet, greet, and talk about ECGridOS, the future of commerce API’s, and partnerships. Please call me if you need info 412-353-9269. But wait, it is not all bad:
Todd will be at the X12 Trimester meeting, so find him or let me help you coordinate a meeting. 412-353-9269
But save the date for 10/15/09 NEECOM.org big user group and ecommerce trade show. The best of its kind. In Massachusetts!
Both Todd and I will be at the NEECOM,org user group meeting. A very active vendor constituency will be there, so call Neecom and get in. The location is at a very reasonably priced hotel outside of Boston…yes, I know, its no Wilshire Grand or Paramount on Telegraph Ave., but its cheap and the company is hip. Loren Data is sure to be hosting an “after the event Chinese buffet for Vendors to recover from the ordeal, everyone is invited including attendees, guests, any NEECOM connected folks. Keep your eye on this blog for time and place as we firm up the precise place.
ECGridOS:
Loren Data is launching a market initiative positioning ECGridOS EDI Global Transit API within the Infrastructure as a Service (IAAS) sector. Alan Wilensky, a B2B sector analyst, will be advising Loren Data Corp on partner and channel development.
Alan is here to serve Loren’s partner and OEM community to help you think about business cases, licensing rationales, and any and all strategic issues impacting EDI communications as an embedded service on YOUR platforms. So we say, Use Him.
Call Alan if you want to discuss the issues related to EDI adoption in the mid-market, and how the API can help you. SAAS, PAAS, and EDI software connector vendors, I fully expect you to pick up that phone at your earliest convenience and call Alan at (412) 353-9269 -
Alan would like to meet with you to see how you have used ECGrid in the past, use it presently and explore ways to use ECGrid and ECGridOS in the future to further expand your business. If you are interested, please drop me a line.
