The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
API / Webservice
Posted: 04 May 06 5:06 AM
|
Abortion Pill Online Ph abortion pill online philippines pankajmishra.net abortion pill online philippines fiogf49gjkf0d Hi
We are currently using the Scribe addon for SLX to add orders, customers, contacts etc into Sales Logix as part of an automated order processing system we have built. The way it works is that an XML is generated from parameters passed into a web portal, the file is FTP'd to the scribe import directory and then Scribe reads the XML and populates SLX tables.
However, we have recently received a new requirement to create a web service which bypasses scribe and returns a unique Order Id on sucessful insertion of the order/customer directly into SLX.
I have looked for an official SLX webservice but one doesn't seem to exist and I have also looked for alternative solutions but can't find anything. The nearest I got was a third party webservices written in .NET which uses direct database inserts to create new orders and customers. This isn't ideal as the database schema is likely to change both internally and in future SLX releases. Does anyone know of a SLX webservice or an API we could use to create our own webservice, ideally in Java?
Thanks
Stuart |
|
|
|
Re: API / Webservice
Posted: 04 May 06 11:22 AM
|
fiogf49gjkf0d Stuart, Sage has not provided an object model for the database. This means you have to write SQL and deal with schema changes when new versions come out.
Make sure your webservice uses the SalesLogix OLEDB provider to modify data. You should be able to use any language you want.
Timmus
|
|
|
|
Re: API / Webservice
Posted: 04 May 06 3:14 PM
|
fiogf49gjkf0d Stuart,
As Timmus mentioned, SLX does not have a web services layer. However, it is easy enough to create your own. I do this all the time (using .NET) and works great. Schema changes will need to be dealt with, but never is too much of an issue (you're not likely to be adding new fields daily or anything, right) |
|
|
|
Re: API / Webservice
Posted: 05 May 06 2:50 AM
|
fiogf49gjkf0d Hi guys, thanks for your feedback, its much appreciated.
Based on your opinions and experience I think I am going to give this a go although I will be attempting to translate the .NET webservice into Java as thats our prefered development language. I haven't used SalesLogix OLEDB before so can you let me know if you think this is feasible? Can it be installed on Linux/Unix based systems? Do you think it can be easily integrated into a Java webapp? When an application is so Microsoft orientated like SLX I am always pessimistic about compatability with non Microsoft technologies!
If I can't use OLEDB, whats stopping me using a standard SQL Server Java API connector to modify the database? |
|
|
|
Re: API / Webservice
Posted: 05 May 06 3:43 AM
|
fiogf49gjkf0d I don't think you can install SalesLogix OLEDB Provider that on a *nix system.
And there's nothing stoppng you from using standard SQL Server Java API to modify the database.
But then you won't be able to use some stored procedure or function that are already embbeded in the SalesLogix OleDbProvider.
If you can justifies the extra works that needs to be done, the you should give it a go
Regards,
Dhany |
|
|
|
Re: API / Webservice
Posted: 05 May 06 11:15 AM
|
fiogf49gjkf0d The SalesLogix OLEDB Provider is no different than *any* OLE DB Provider. It doesn't have to be programmed against using a MS development envrironment, but it does have to be used from an environment that can use OLEDB/ADO/ETC. It will not install on a *nix system.
If you don't use the SLX provider then you won't be able to use built in functions to create table ID values and etc. You won't have any of the SLX security built in, and worst is that none of your data will synchronize to remotes. |
|
|
|
Re: API / Webservice
Posted: 13 May 06 3:37 PM
|
fiogf49gjkf0d Yeah personally I have been trying to discourage making direct SQL connections more and more lately, especially with Scorpion around the corner supporting custom OLE-DB provider extensions (add your own security model, add your own functions, build defaulting rules).
You can use direct SQL from *nix, but it is a complex decision. You absolutely should not if a) you don't know whether SalesLogix security will be applied (or you know that it will be), b) you are building this out for potentially more than one install base that might have different needs, or c) there is any remote possibility that there may be a migration path to Scorpion (v7) in association with this web services platform and there is any possibility that OLE-DB extensions could be taken advantage of for any reason. |
|
|
|
Re: API / Webservice
Posted: 24 Jan 08 11:09 PM
|
| Picking up on a pretty old thread here, but is it still the case in version 7.2 that there is no standard web services API provided? We still need to roll our own web service using SQL calls underneath? We're at 6.2 looking to upgrade and having a standard web services API would be a big win. |
|
|
|
Re: API / Webservice
Posted: 24 Jan 08 11:23 PM
|
Originally posted by Tom
Picking up on a pretty old thread here, but is it still the case in version 7.2 that there is no standard web services API provided? We still need to roll our own web service using SQL calls underneath? We're at 6.2 looking to upgrade and having a standard web services API would be a big win. |
|
That is correct - no web services layer exists now. However, that is coming in a future version. For now you just have to roll your own.
-Ryan |
|
|
|