I have a project that I need to build that gathers data from a local database, packages it into an xml file (as specified by receiving server) and send it to another server via an API they provide.
I then need to be able to receive data back from that remote server and display it to the user (or users).
I know how to get the data and package it. I'm just not sure how to do the part that sends it to a remote server via their API and receive data back from them.
A user needs to be able to access the system (with secure login) and simply tell it what data is needed (by selecting a case) then clicking a button or something to initiate the process of sending out the data and then waiting for a response.
The 2 ways I thought about doing this are: 1. Build a web app to deploy on the local server that has the user interface - it is self-contained and doesn't need to communicate with a client - just the other remote server. Once the user logs in and initiates the data exchange, the app would process everything and send it to the remote server, then receive the response and notify the user and display it.
2. Build a client that the user accesses and the client would gather the necessary data, then send it to the local server in some manner (xml, json, whatever), then the local server would process it and package it appropriately and send it to the remote server. Then, when a response was received, it would notify the client and send the response back to the client.
The problem is that I'm not sure what type(s) of apps to use to accomplish this. I'm fairly new to visual studio, but I know how to get the data and package it and once data is received from the remote server, I know how to de-serialize it and display it. I just am not sure how to manage the communications between the servers and/or the client.
If someone can steer me in the direction I should look, I would greatly appreciate it. I was thinking of doing an MVC app for the server portion, but I don't know enough about it to know if that's the best way to go or if it's only part of the solution.
Do I need 1 app or several working together? I would prefer to just do a web app, but may need to do the client / server depending on issues yet to be finalized.
Thanks,
Ron
I then need to be able to receive data back from that remote server and display it to the user (or users).
I know how to get the data and package it. I'm just not sure how to do the part that sends it to a remote server via their API and receive data back from them.
A user needs to be able to access the system (with secure login) and simply tell it what data is needed (by selecting a case) then clicking a button or something to initiate the process of sending out the data and then waiting for a response.
The 2 ways I thought about doing this are: 1. Build a web app to deploy on the local server that has the user interface - it is self-contained and doesn't need to communicate with a client - just the other remote server. Once the user logs in and initiates the data exchange, the app would process everything and send it to the remote server, then receive the response and notify the user and display it.
2. Build a client that the user accesses and the client would gather the necessary data, then send it to the local server in some manner (xml, json, whatever), then the local server would process it and package it appropriately and send it to the remote server. Then, when a response was received, it would notify the client and send the response back to the client.
The problem is that I'm not sure what type(s) of apps to use to accomplish this. I'm fairly new to visual studio, but I know how to get the data and package it and once data is received from the remote server, I know how to de-serialize it and display it. I just am not sure how to manage the communications between the servers and/or the client.
If someone can steer me in the direction I should look, I would greatly appreciate it. I was thinking of doing an MVC app for the server portion, but I don't know enough about it to know if that's the best way to go or if it's only part of the solution.
Do I need 1 app or several working together? I would prefer to just do a web app, but may need to do the client / server depending on issues yet to be finalized.
Thanks,
Ron