Configuration and Administration
glog.ExternalDistanceEngine Properties
To control the behavior of Oracle Transportation Management, you can change settings in the glog.properties file or the appropriate property set.
Note: PC*Miler ASMX based web service (ASP.NET Web Service) has been deprecated as of 6.4.3 release and will be removed from future release. You have OTM integrated with PC*Miler WCF (Windows Communication Framework) based web service.
Property |
New in Version |
Description |
---|---|---|
glog.ExternalDistanceEngine.EDEType.Gid.<external distance engine type> | This property identifies the external distance engine type for EDE/ESE defined to connect using the generic web service client. | |
glog.ExternalDistanceEngine.EDEType.weightRange.glog.business.rate.ratedistance.external.<EDE class name> The EDE classes are:
|
20A |
This property works along with glog.ExternalDistanceEngine.useNewEDECache. It allows you to define weight ranges if you use dynamic attributes. You get the EDE class name when you create the external distance engine. Enter weight ranges as a comma separated array. That means that multiple ranges are added on the same property separated by a comma. For example, you could have the following: 0 LB-14000 LB,14000 LB-28000 LB,28000 LB-48000 LB In this case, 14000 is listed as a high value and a low value. You may not want to enter 14001 as a high value in case something weighs 14000.5 LBS. With using the same high and low value, no weight will be excluded. If the same value is used as both high and low value, it will be considered as part of the lower range. If using more than one EDE, each EDE should have it's own property valued. The default is 0 LB-60000 LB. |
glog.ExternalDistanceEngine.EDEType.weightRange.glog.business.rateservicescheduling.external.<ESE class name> |
20A |
This property works along with glog.ExternalDistanceEngine.useNewEDECache. It allows you to define weight ranges if you use dynamic attributes. You get the ESE class name when you create the external service engine. If using more than one ESE, each ESE should have it's own property valued. The default is 0 LB-60000 LB. See the following property for more details: glog.ExternalDistanceEngine.EDEType.weightRange.glog.business.rate.ratedistance.external.<EDE class name> |
23A |
This property is used to enable or disable geocoding using the data in the table GEO_POSTAL_POINT and set latitude/longitude to a location. For geocoding, the locationfor both latitude and longitude have to be empty. When the property value is set to true, the application enables the automatic lookup for latitude/longitude based on the postal code and adds latitude/longitude to a location. If the property value is set to false, the application doesn't geocode. |
|
21A |
Specifies the type of authentication you want to use for HERE. It can take one of the following values, which are case-sensitive:
Note: This property should not be used when using external distance/service time engine as HERE Routing (version 8). |
|
glog.ExternalDistanceEngine.HERE.v8.healthcheck.<parameter> | 24A |
Defines how HERE is configured to work with the external system health check. The property takes the following parameters:
|
glog.ExternalDistanceEngine.HERE.v8.sectionElementForDistanceTime | 22A |
This property specifies the element under which the distance and time results are retrieved in the response received from HERE Routing version 8. Default: summary |
glog.ExternalDistanceEngine.HERE.v8.throwException.section.CriticalNotices |
22A |
This property specifies whether exceptions must be thrown for critical notices received under the section element in the response from HERE Routing version 8. Default: true |
glog.ExternalDistanceEngine.HEREGeocoding.navigateToAccess | 23A |
This property controls the derivation of latitude/longitude using position or access elements in the response received from HERE Geocoding. When the property value is set to true, it will use the access element; when the property value is set to false, it will use the position element. Default: false |
glog.ExternalDistanceEngine.HEREGeocoding.healthcheck.<parameter> |
24A |
Defines how HERE Geocoding is configured to work with the external system health check. The property takes the following parameters:
|
6.4.2 |
Controls the protocol information provided to the Oracle Map Cloud Services Engine. Based on the value of this property, the request URL would be formed in the OracleSpatialEngine code. Default: http For http, a sample URL would look like: http://elocation.oracle.com:80/routeserver_eu/servlet/RouteServerServlet For https, a sample URL would be: https://elocation.oracle.com/routeserver_eu/servlet/RouteServerServlet See the property OracleSpatial.Port for setting the port value. |
|
6.4.2 |
Stores the authorization key to validate PC*Miler RAIL Web Services. This property is used for authorization purpose of PC*MILER RAIL Web Services. See Configuring PC*Miler Rail Web Services. |
|
glog.ExternalDistanceEngine.PCMilerRailWS.healthcheck.<parameter> |
24A |
Defines how PC*Miler is configured to work with the external system health check. The property takes the following parameters:
|
6.3.2 |
Specifies the account details to log on to the external distance engine. The password is stored in the OTM Wallet under the glog.ExternalDistanceEngine.PCMilerWS.Account wallet key. To set this, use the property set or directly modify the OTM Wallet. |
|
6.4.2 |
Stores the authorization key to validate PC*Miler WCF Web Services. This property is used for authorization purpose of PC*Miler WCF Web Services. See Configuring PC*MILER Web Services. |
|
6.4.2 |
This property enables you to access distance or time of a specific version of PC*MILER Web Services. The value corresponds to the PC*Miler version. Note: You should not use an older version of PC*Miler than 30 if using European locations when generating rush hour data. |
|
glog.ExternalDistanceEngine.PCMilerWS.EqRestrictions.Dimensions.Rounding |
This property defines the rounding of equipment dimensions for PC*Miler WCF Web Services. Default: CEIL |
|
glog.ExternalDistanceEngine.PCMilerWS.healthcheck.<parameter> | 24A |
Defines how PC*Miler Web Services is configured to work with the external system health check. The property takes the following parameters:
|
6.3.2 |
Specifies the password needed to access the external distance engine. The password is stored in the OTM Wallet under the glog.ExternalDistanceEngine.PCMilerWS.Password wallet key. To set this, use the property set or directly modify the OTM Wallet. |
|
6.3.2 |
Specifies the user name needed to access the external distance engine. The password is stored in the OTM Wallet under the glog.ExternalDistanceEngine.PCMilerWS.Username wallet key. To set this, use the property set or directly modify the OTM Wallet. |
|
6.4.2 |
The default URL for non-HTTPS WCF Web Services: http://pcmiler.alk.com/APIs/SOAP/v1.0/Service.svc?wsdl The default URL for HTTPS WCF Web Services: https://api.trimblemaps.com/pcmws/v1/soap/service.wsdl To change this URL to secure URL (using HTTPS as protocol), use this property. |
|
6.4.2 |
This property specifies the WSDL URL for the PC*Miler Web Service. The default URL for ASMX Web Services is "http://pcmws.alk.com/?wsdl" and the supported https WSDL URL is "https://pcmws.alk.com?wsdl". |
|
glog.ExternalDistanceEngine.PCMilerRailWS.WsdlUrl |
This property specifies the WSDL URL for the PC*Miler Rail Web Service. The default URL is "https://pcmrail.alk.com/SOAP/v22.0/Service.svc?wsdl". |
|
20A |
With this property, OTM will use caches that are EDE/ESE specific (below). With these caches, OTM will reduce the hits on the EDE when Dynamic Attributes (including Length, Width, Height, Weight and HAZMAT) are involved. This property works when set to true (the default is false) and the cache control type is set to "Cache by Xlane Don't Lookup - Don't Save". The weight range comes from the property: If set to false, normal caches will be used that use the source/destination location pair as well as the RateDistancePk/RateServicePK to cache the Rate Distance/Service Time from EDE/ESE. This causes an issue whenever dynamic attributes are involved (the value retrieved from the cache could be incorrect) since dynamic attributes affect the shipment route and hence the rate distance. If using dynamic attributes, you should set this to true. The following EDE/ESE specific caches all have a default of 40000: glog.cache.RateDistanceCache-HERE.capacity glog.cache.RateDistanceCache-ALK.capacity glog.cache.RateDistanceCache-OracleSpatial.capacity glog.cache.RateDistanceCache-ExtWebService.capacity glog.cache.RateServiceCache-HERE.capacity glog.cache.RateServiceCache-ALK.capacity glog.cache.RateServiceCache-OracleSpatial.capacity glog.cache.RateServiceCache-ExtWebService.capacity |