mirror of
https://github.com/nsnail/Ocelot.git
synced 2025-04-22 13:22:50 +08:00
454ba3f9a0
* test for issue * added service fabric sample * working!! * changed sample naming to Ocelot * removed files we dont need * removed files we dont need * updated sample gitignore * updated sample gitignore * getting ocelot to work with service fabric using the reverse proxy * #238 - added support for service fabric discovery provider, proxies requests through naming service, wont work on partioned service fabric services yet * #238 - Manually tested service fabric using sample..all seems OK. Made some changes after testing, added docs * #238 - added docs for servic fabric
36 lines
1.4 KiB
ReStructuredText
36 lines
1.4 KiB
ReStructuredText
Service Fabric
|
|
==============
|
|
|
|
If you have services deployed in Service Fabric you will normally use the naming service to access them.
|
|
|
|
The following example shows how to set up a ReRoute that will work in Service Fabric. The most important thing is the ServiceName which is made up of the
|
|
Service Fabric application name then the specific service name. We also need to set UseServiceDiscovery as true and set up the ServiceDiscoveryProvider in
|
|
GlobalConfiguration. The example here shows a typical configuration. It assumes service fabric is running on localhost and that the naming service is on port 19081.
|
|
|
|
The example below is taken from the samples folder so please check it if this doesnt make sense!
|
|
|
|
.. code-block:: json
|
|
|
|
{
|
|
"ReRoutes": [
|
|
{
|
|
"DownstreamPathTemplate": "/api/values",
|
|
"UpstreamPathTemplate": "/EquipmentInterfaces",
|
|
"UpstreamHttpMethod": [
|
|
"Get"
|
|
],
|
|
"DownstreamScheme": "http",
|
|
"ServiceName": "OcelotServiceApplication/OcelotApplicationService",
|
|
"UseServiceDiscovery" : true
|
|
}
|
|
],
|
|
"GlobalConfiguration": {
|
|
"RequestIdKey": "OcRequestId",
|
|
"ServiceDiscoveryProvider": {
|
|
"Host": "localhost",
|
|
"Port": 19081,
|
|
"Type": "ServiceFabric"
|
|
}
|
|
}
|
|
}
|