Tutorials och dokumentation
Tickstar delar gärna med sig av sin kunskap. På denna sida hittar du information relaterat till den teknik Tickstar använder.
Tickstar EDIFACT Webservices Frequently Asked Questions
What is Tickstar EDIFACT Webservices?
It’s a free-to-use1, public webservice that enables transformation from EDIFACT to XML and vice versa. The service is delivered over the internet as a cloud service and can be used by anyone that needs to transform EDIFACT to/from XML without having to invest in locally managed tranformation/conversion tools.
EDIFACT is well spread and supports many Business-to-Business processes, such as the order and invoicing process with trading partners as well as processes for logistics and transportation.
The XML that Tickstar EDIFACT Webservices generate is an ”EDIFACT-ish” XML. The EDIFACTs generated are according to Unece’s specifications.
1D.96A and D.97A are offered at no cost and without support. Hence, it’s delivered with no guarantees.
Which EDIFACT message types and versions are supported?
Here are the D.93A to D99.B and D.00A to D08.B supported message types and versions. If you need other EDIFACT message types, notify us and we’ll help you promptly.
Can we use the service at no cost?
Yes, as long as you use the schemas and versions1 offered.
If you require custom transformations – others than the ones supported (se above) – you might consider the cloud service Tickstar Nova or Tickstar Integration Platform.
How do we know that the service really works?
We’ve been doing this for 10 years with satisfied customers.
But what happens if something goes wrong?
We’ve done everything to make this service as secure, reliable and usable as possible. However, please note that we do not guarantee anything in the free version.1
If you plan to use the webservice in a business critical process or want any of the following; require a certain service level (SLA), want to be able to talk to our support engineers, get necessary expertise help, monitor transactions and be able to Track & Trace in order to hunt down errors (which in most cases are caused by bad data – as you already know) you might consider the add-on services we offer for Tickstar EDIFACT Webservices.
Ok, so how do we get started?
Read the Tickstar EDIFACT Webservices tutorial that will help you out to use it.
Help us to help you even more
If you find a bug or have a feature request, just write an email hidden; JavaScript is required to our Support Engineers.
Tickstar EDIFACT Webservices Tutorial
Tickstar EDIFACT Webservices is a free-to-use1, public webservice that enables transformation from XML to EDIFACT and from EDIFACT to XML.
If you already read the FAQ, you’re all set to begin!
1D.96A and D.97A message types are available at no cost. Here are the D.93A to D99.B and D.00A to D08.B supported message types and versions.
The webservice is described with this email hidden; JavaScript is required and consists of the following operations:
GetSupportedServicesEdifactToXmlxmlToEdifact
GetSupportedServices
By using this operation you can check if a specific EDIFACT-transformation is available. It has three optional input parameters
message: message type, i.e APERAK, IFTSTA, IFTMIN or INVOICdirectory: message version, i.e d96asyntaxVerson: EDIFACT syntax version, i.e 3 or 4.
The response to a GetSupportedServices request is a list of all the message types that matched the posted search criterias.
Posting ”message=IFTMIN” will give you a list of all the catalogues supported for that specific message type.
The response will also contain the schemaURL wich is the location of the XML schema.
For a complete list of supported message types and element descriptions, please refer to the UN/CEFACT EDIFACT specifications that can be found here for the versions D.93A to D99.B and D.00A to D08.B.
If you need other message types, notify us and we’ll help you promptly.
xmlToEdifact
xmlToEdifact converts an XML post to the corresponding EDIFACT according to the schema received using the GetSupportedService.
This operation has to contain an EdifactHeader element of the same type as in GetSupportedServices. Please note that all fields are mandatory; message, directory and syntaxVersion.
The posted XML message will be transformed with the schema specified in the operation GetSupportedServices.
The response will be the corresponding EDIFACT message in the payload field, encoded with base64.
EdifactToXml
EdifactToXml converts an EDIFACT post to the corresponding XML according to the schema received using GetSupportedService.
This operation has to contain an EdifactHeader element of the same type as in GetSupportedServices. Please note that all fields are mandatory; message, directory and syntaxVersion.
The posted EDIFACT message will be transformed with the schema specified in the operation GetSupportedServices.
The response will be the corresponding XML message in the payload field, encoded with base64.
Help us to help you better
If you find a bug or think that this tutorial is incomplete or contains errors, please leave a comment below or email hidden; JavaScript is requiredwrite an e-mail to us so that we can fix it.
Presentation från Open ESB-seminarium
Nu är Presentationen från vårt Open ESB-seminaruim den 29 april 2008 tillgänglig för nedladdning.
Du hittar den här:
Screencasts från demonstrationerna kommer inom kort.
Presentation från Sun Nordic Software Roadshow
Tickstars presentation om Open ESB från Sun Nordic Software Roadshow i Göteborg och Stockholm den 10 och 12 Mars 2009 finns tillgänglig för nedladdning här:
Dynamisk routing av JMS från BPEL
Många gånger är vill man kunna välja JMS-kö utifrån innehållet i ett meddelande. Detta är möjligt att göra med hjälp av partner-link-properties i en BPEL-process.
Följande exempel beskriver hur detta går till:
Orderintegration med Glassfish ESB del 2 – integration
Detta är del två ett exempel som visar hur en integration kan göras med hjälp av JCAPS eller Open ESB.
I denna del visar jag hur själva integrationen byggs.
Klicka på länken för att titta på videon
Orderintegration med Glassfish ESB del 1 – Custom encoding
Detta är del ett i ett exempel som visar hur en integration kan göras med hjälp av JCAPS eller Open ESB. I denna del visar jag hur man skapar ett schema för ”custom encoding” av ett godtyckligt flatfilsformat.
Följande exempel beskriver hur detta går till:
Minneshantering i Java CAPS
Ett komplicerat område inom java är tuning av parametrar för minnestilldelning och garbage collector. 
Följande dokument ger en introduktion till tuning av minnesparametrar i JavaCAPS.
