Skip to content

Latest commit

 

History

History
150 lines (106 loc) · 4.98 KB

README.md

File metadata and controls

150 lines (106 loc) · 4.98 KB
Raw

proxy-net

Coverage Release Tagging Test

Description

Proxy service intended to forward traffic between clients and gateway-java so they don't need to suffer SOAP

Step for running the PROXY-NET

Clone the repo:

git clone https://github.com/hawks-atlanta/proxy-net.git

Enter the new folder:

cd /proxy-net

Convert: CRLF to LF the file .docker-psql-mult-db

You can setup the necessary services by running:

docker compose up -d

Services port & route:

http://localhost:8084/ROUTES

Note: In the Docker-Compose FILE edit the service you want to test with, for development use the same service that the gateway container provides and for production the URL of your ONLINE service.

Example:

In Docker-Compose:

  # Proxy-net
  # Local/Docker http://gateway:8080/gw/service (Gateway Container)
  # Remote       http://URL-YOUR-SOAP-PR/service
....
    environment:
      - SERVICE_URL=http://localhost:8080/gw/service

Note: It is not necessary to add ?WSDL | connect to Localhost with using name "gateway" container

With this config of Docker-Compose is auto impl in DockerFile:

...more lines
ARG ASPNETCORE_URLS
ARG SERVICE_URL
ENV ASPNETCORE_URLS=$ASPNETCORE_URLS
ENV SERVICE_URL=$SERVICE_URL
...more lines

For Development

Opening the project

  1. Double click on the solution file. It will open the solution in your current version of the Visual Studio 2022.
  2. (Click in button Docker)
  3. Install Nuget Packages

Restoring project's dependencies

  1. In the Visual Studio, open the Package Manager Nuget and run the command to restore all packages used by the API. You can also click-right on the solution's name in the Solution Explorer and select "Restore NuGet Packages.
dotnet restore

Building & Running the API

  1. To build the project you have two options: The first one is click-right on the solution's name and then select "Build Solution". The second option is by running the command below through the Package Manager Console terminal;
dotnet build
  1. To Run the API, there are also two options: Pressing F5 or executing the command through the terminal.
dotnet run

⚠️WARNING! for updates in Gateway-SOAP:

Change ${SERVICE_URL} to http://localhost:8080/gw/service?wsdl dotnet-svcutil.params.json:

{
  "providerId": "Microsoft.Tools.ServiceModel.Svcutil",
  "version": "2.1.0",
  "options": {
    "inputs": [
      "http://localhost:8080/gw/service?wsdl"
    ],
 //More lines...

For update Reference.cs:

dotnet svcutil -u ServiceReference http://localhost:8080/gw/service?wsdl

Revert change "CTRL + Z" the file dotnet-svcutil.params.json change to:

{
  "providerId": "Microsoft.Tools.ServiceModel.Svcutil",
  "version": "2.1.0",
  "options": {
    "inputs": [
      "${SERVICE_URL}"
    ],
  //More lines...

To add the service either localhost or remote from the SOAP GATEWAY, the ENV SERVICE_URL reading is created, in the file References.cs implement this code:

private static System.ServiceModel.EndpointAddress GetEndpointAddress(EndpointConfiguration endpointConfiguration)
{
    if ((endpointConfiguration == EndpointConfiguration.ServiceImpPort))
    {
        string serviceUrl = Environment.GetEnvironmentVariable("SERVICE_URL");
        if (string.IsNullOrEmpty(serviceUrl))
        {
            throw new ApplicationException("SERVICE_URL env not found!");
        }
        return new System.ServiceModel.EndpointAddress(serviceUrl);
    }
    throw new System.InvalidOperationException(string.Format("No se pudo encontrar un punto de conexión con el nombre \"{0}\".", endpointConfiguration));
}

🚨**NOTE!: **When you want to make a new update to the interface provided in the References file you need to add this line of code, be careful not to touch other lines of code!