|
Frequently Asked Questions
|
|
If you have RemoteXerver questions you want answered or issues you
need resolved, just email us via the Contact Us
page on this website. We are looking to expand this section, so please email
us your questions.
|
|
| |
|
|
|
| |
| |
 |
| |
|
What is RPC?
|
|
RPC allows one program to make a procedure call to another program.Since the two systems may be on different computers or even end of the world, this is referred to as a Remote Procedure Call (RPC). RPC communications occur between two programs. The Client side is the one that initiates the RPC and the Server side is the one that executes the desired procedure and returns results. Client and Server may reside on the same machine. Only the relationship between the two applications determines which is the Client and which is the Server.
|
| |
 |
| |
|
What is XML-RPC?
|
|
XML-RPC is a simple, portable way to make remote procedure calls over HTTP (Hypertext Transfer Protocol – the way browsers communicate with servers over the Web). It uses a standardized XML document to hold the request and response for the RPC. What happens is the Client application calls a separate application, known as an XML-RPC Client, telling it where to find a desired Server application, what procedure to call, and what variable to pass to it. The XML-RPC Client is responsible for wrapping all this up in an XML document and sending it to an application on the Server. This application is an XML-RPC Service. The XML-RPC Service reads the XML doc and figures out how to handle it. It calls the Server application, gets the results, wraps them into another XML doc and passes it back to the XML-RPC Client. The XML-RPC Client then passes the results back to the Client application.
The benefit of XML-RPC is that it uses a standard XML document for communication. This means that the Client and Server sides can be written in completely different languages by different people. As long as they both know the procedures and variables that will be passed the whole process should work.
Please visit the XML-RPC Home Page for more information.
|
| |
 |
| |
|
What is RemoteXerver?
|
|
RemoteXerver is an XML-RPC framework written in the ProvideX programming environment. This allows programs written in PVX running on one system to communicate with programs on another system over the Internet. Since XML-RPC is an industry standard, RemoteXerver allows PVX programs to communicate with programs written in any other programming languages. Because of this, PVX programs can communicate with web-enabled devices such as PDAs and Cell Phones.
|
| |
 |
| |
|
What is a Web Service?
|
|
RemoteXerver comes with three Web Services:
Customer Web Service [Set | Get] - Create, Modify and Retrieve MAS 90 Customer Information Sales Order Web Service [Set] - Create MAS 90 Sales Orders Generic Row Retrieval [Get] - Retrieve a record from any MAS 90 Business Framework datafile
A description of each is provided in the Web Services page. Other Web Services can be written by any Sage Master Developer.
|
| |
 |
| |
|
What's included in RemoteXerver?
|
|
RemoteXerver comes with three Web Services:
Customer Web Service [Set | Get] - Create, Modify and Retrieve MAS 90 Customer Information Sales Order Web Service [Set] - Create MAS 90 Sales Orders Generic Row Retrieval [Get] - Retrieve a record from any MAS 90 Business Framework datafile
A description of each is provided in the Web Services page. Other Web Services can be written by any Sage Master Developer. Source Code is provided to any Sage Authorized Master Developer to get them started.
|
| |
 |
| |
|
Where do I get support?
|
|
RemoteXerver is a developer tool that allows you to create websites, in a variety of languages, that post information to MAS 90 via Web Services created by you or delivered with RemoteXerver.
HighTower can work with your web development team, helping them communicate with RemoteXerver, and with your Master Developer, helping them develop their Web Services.
|
| |
 |
| |
|
Where can I get a new Web Service created?
|
|
Web Services can be written by any Sage Master Developer, contact HighTower for help finding a local resource.
|
| |
| |