Web Services with MySQL Interaction (Server and Client)
$100-150 USD
Paid on delivery
There are two deliverables in this project:
1) Server Side Software
The Web Service "Server" shall be written in Java and be deployable as a war file on a Glassfish Server. Code should be protected by a license that is dependent on the machine id and that expires after a configurable time. After expiry, a new license would be needed on the server to continue using the system.
2) Client Side Software
The Client Web Services shall be written in Visual Basic 6 language. Code will be added in an existing Visual Basic Project, and so details on how to integrate this new Client Side code in a Visual Basic 6 Form shall be provided. Code that enables the protection by a license key that is dependent on the machine id and that expires after a configurable time shall also be provided. Note that after expiry, a new license would be needed on the server to continue using the system. This licensing code will also be added on the current Visual Basic Project.
## Deliverables
Below are details on the Request/Reponses that will be used in the system.
## The newFile Request
The newFile Function will be implemented as a WSDL Web Service where the following parameters will be passed:
? Clinic
? Ramq
? CareId
### When the Server side receives the newFile query, it will populate a new entry in a MySQL Database Table. The Database and Table that will be used is provided as an additional file below.
Below is a description of the parameters passed to the Request.
### Clinic
Text Field
### Ramq
Ramq is a 12 character alphanumeric Id
### CareId
CareId is an integer id
## The newFile Response
The response to this request will be a simple Success of Failure Response from the Web Service. In case of Failure, and explanation shall be included in the Response Packet.
## The findFiles Request
The findFiles Request will be implemented as a WSDL Web Service where the following parameter will be passed:
? CareId
## Upon receiving the Request, the service shall query the database table for all the {Clinic, Ramq, and Paths} sets that are associated with the CareId provided.
Below is a description of the parameter passed to the Request.
## CareId
CareId is an integer
## The findFiles Response
The findFiles Response will be an XML document that will contain sets representing the Files that are available in all the different clinics. The following information will be in each set returned:
? Clinic
? CareId
? Ramq
? Path
### Below is a description of the parameters passed to the Request.
### Clinic
Clinic is a text field
**Ramq**
Ramq is a 12 character alphanumeric Id
CareId
CareId is an integer id
### Path
Path is a variable that represents the exact path where the eFile at the specified clinic can be pulled from. This is computed as follows:
"\\$Clinic\$CareId\$Ramq
Project ID: #3459980