...
Release Note - Virtualiseringsplatformen, för att läsa om förändringar mellan olika versioner
Instruktion för sensate versionen av VP - 2.2.
...
8
Release Note - Virtualiseringsplatformen, förändringar i properties sedan tidigare versioner
...
Kodblock |
---|
# Overrides applications default vp-config.properties ############################################################################################### # Comma separated list of ip addresses that should be valid to call virtual services (VP) # using http (and of course valid headers for authorization). When using https this list # is not used. # # IP_WHITE_LIST=127.0.0.1,127.0.0.X,127.0.0.Y ############################################################################################### IP_WHITE_LIST=<your list> # Standard properties for an external ActiveMQ broker, see soitoolkit-mule-jms-connector-activemq-external.xml. SOITOOLKIT_MULE_AMQ_BROKER_URL=failover:(tcp://<your host x>:61616,tcp://<your host y>:61616) ############################################################################## # Properties for service "VagvalRouter" # # Mandatory comma separated list of ip addresses (or subdomains, e.g 127.0.0 for all ip adresses under that domain) # that should be valid to call virtual services (VP) using http (and of course valid headers for authorization). # When using https this list is not used. # # IP_WHITE_LIST=127.0.0,127.1.2.3,127.4.6.7 # # Mandatory identifier of this VP instance to be used when communicating over http with other # SKLTP components # # VP_INSTANCE_ID=THIS_VP_INSTANCE_ID # # Optional http header to be used by e.g a load balancer to set the sender ip adress. A typical scenario # is when a service consumer calls VP through a load balancer and VP would like to have information # regarding the consumers ip adress. # # VAGVALROUTER_SENDER_IP_ADRESS_HTTP_HEADER=X-Forwarded-For # ############################################################################## TP_SOKVAGVALSINFO_URL=http://ine-sit-app01:8085localhost:8080/tp-vagval-admin-services/SokVagvalsInfo/v2 VP_INSTANCE_ID=<YOUR VP INSTANCE ID> ###VAGVALROUTER_SENDERID=2.5.4.5 VAGVALROUTER_SENDERID=OU ################################################################# # Properties for service "resetVagvalCache" # # RESETVAGVALCACHE_INBOUND_URI=URI for reset cache # RESETVAGVALCACHE_PORT=Port number for reset cache # LOCAL_TAK_CACHE=Path to file where local TAK cache should exist # Default LOCAL_TAK_CACHE=${user.home}${file.separator}.tk.localCache ################################################################# LOCAL_TAK_CACHE=<your>/<path>/<to>/.tk.localCache ##################################################################################################### # HSA cache properties # # # # HSA_FILES=<file1,file,filex> # ##################################################################################################### # List if files to be read by HSA cache, first file is master, rest is complementary HSA_FILES=<your>/<path>/<to>/hsacache.xml,<your>/<path>/<to>/hsacachecomplementary.xml ############################################################################################################# # Response timeout Feature properties # It is possible to control response timeout on each service in VP, if the service supports it. # Default values for all services are defined in SERVICE_TIMEOUT_MS, to override follow the convention # described below and make sure the service to use supports this feature. # # Convention: feature.featureresponsetimeout.<service contract namespace>=5000 # Example: feature.featureresponsetimeout.urn.riv.crm.scheduling.GetSubjectOfCareScheduleResponder.1=5000 ############################################################################################################# # Default timeout for synchronous services SERVICE_TIMEOUT_MS=30000 feature.featureresponsetimeout.druglogistics.dosedispensing=5000 #Infektionsverktyget feature.featureresponsetimeout.urn.riv.processdevelopment.infections.DeleteActivityResponder.1=5000 ##################################################################################################### # Keep alive Feature properties # It is possible to control keep-alive settings on each service in VP. If a service has keep-alive # # enabled all consumers and producers are affected. Default setting is used by all services and # # is set to feature.keepalive=false. To enable keep-alive for one service use this convention: # # Convention: feature.keepalive.<service contract namespace>=true # # Example: feature.keepalive.urn.riv.crm.scheduling.GetSubjectOfCareScheduleResponder.1=true # ##################################################################################################### #Default setting is false, used by all services that does not specify any specific configuration feature.keepalive=false feature.keepalive.urn.riv.crm.scheduling.GetSubjectOfCareScheduleResponder.1=false |
...