...
Appsettings.json
Update these URL’s to match the customer server name
"BaseUrl": "https://unityserver/UnityTest/",
"IdentityUrl": "https://unityserver/UnityTest/"
"PublicOriginUrl": "https://unityserver/UnityTest" **No trailing backslash
Update Log settings - depending on whether you want a lot of logging or the minimum, set appropriately based on the below settings.
For more logging:
Code Block "LogLevel": { "Default": "Debug" "RequestTracingEnabled": true,For less logging:
Code Block "LogLevel": { "Default": "Warning" "RequestTracingEnabled": false,
Update Application Insights Key (get from dev ops)
Code Block "ApplicationInsights": { "InstrumentationKey": "KEY-HERE"
nLog.config - contains more log settings and also the same Application Insights Key as the appsetting.json. Whenever you want to setup more logging, change these settings along with the above and then change them back when you want less logging.
For more logging
Code Block <!--All logs, including from Microsoft--> <logger name="*" minlevel="Trace" writeTo="allfile" />
For less logging
Code Block <!--All logs, including from Microsoft--> <logger name="*" minlevel="Warn" writeTo="allfile" />
Update or add Application Insights key
Code Block <target xsi:type="ApplicationInsightsTarget" name="aiTarget"> <instrumentationKey>KEY-HERE</instrumentationKey> </target>Set minLevel to “Info' (search file for this as there are several entries that are very similar)
Code Block <logger name="*" minlevel="Info" writeTo="aiTarget" />
identity-config.json - this files contains the Unity ClientID, ClientSecret and all the scopes Unity supports. We have a tool that can create the ClientSecret as a hash value so check with Kevin on this.
Update ClientID and ClientSecrets value
Code Block "ClientId": "AWUnity", // a client credentials client "ClientSecrets": [ { "Value": "7m3TYF4oCJ4KzC9MBDXrX8/SDBgyBpQimcB859nZOYo7m3T***********************OYo=" } ],Scopes - we don’t typically have to adjust these but we do occasionally add new ones. For example, when AW Payment Plans were added, we added the ‘service.payment’ scope so that needed to be added to each customer using this functionality.
Code Block "Name": "service.payment", "Scopes": [ { "Name": "service.payment" } ] } "AllowedScopes": [ "services", "service.user", "service.customer", "service.entitlement", "service.media", "service.product", "service.order", "service.itinerary", "service.worker", "service.access", "service.contact", "service.account", "service.loyalty", "service.payment" ],
Rtp-config.json – contains RTP database, server and SQL login info, as well as RTP admin settings. We occasionally add to the list of settings with new versions and these settings need to be added manually because we do not update the rtp-config.json file with each Unity auto-deployment. Below is a list of settings and descriptions.
| Set to either, 2014.2.0.14 or 2016.1.1.7 depending on the version of RTP being used. This determines how credit cards are saved into RTP. | ||
|---|---|---|---|
| Used to create the RTP Alternate ID Profile. Update ‘PK’ to whatever makes sense for each resort. Do not change after customers start logging in. | ||
| Set value to match the RTP RoleCode for a ‘relative'. This value can be found in RTP admin or the database in the Role table. | ||
| Set value to a newly created ProfileType code in RTP (always set these two settings to the same value). AW recommends creating a new Profile Type rather than using an existing on. After this is created, a new entry in RTP admin needs to be created in Profile Type for Profiles. | ||
| Set value to the Sales Channel Code being used by the Commerce site. | ||
| Set Value to the IPTypeCode for the Temporary Customer entry in the IPType table (usually 3010 but some customers are different) | ||
| No longer used. This setting can be removed. | ||
| Set value to the RTP Inventory Location Code being used for RTP retail inventory sync. | ||
| Set value to Base is using Unity for Order Processing or Connect is using RTPConnect for Order Processing. | ||
| These settings are only used if the above setting, “OrderProcessor” is set to Connect. If set to Connect, define the RTP Connect URL in the RTPConnectURL field and set SSLEnabled accordingly. | ||
| Set value to true if AW Payment Plans are being used. If AW payment plans are not being used, this setting can be left as true or could be omitted from file. | ||
| Set to true if an alternate stored procedure is being used for RTP inventory pool inquires (i.e. AW_proc_publicGetProductInventoryPoolInventory.sql). Set to false (or remove setting) if the standard RTP inventory pool stored procedure is being used. | ||
| These settings are used in conjunction with AW Additional Payments. Define the general product header codes created for AW additional payment functionality along with the RTP Payment Method codes for voucher payments, gift cards and stored value. | ||
| Define an RTP UserID that will be added as the OperatorID for anything created from the site (Customer Manager Profiles, Orders, Transactions, etc.) | ||
| Define the RTP Currency Code being used by the site. Typically this is set to 1 | ||
| Set PaymentMethodCodeOrder to a newly created AW Clearing Payment Method code from RTP and set the PaymentMethodCodeFulfillment code to the RTP Deposit Applied Payment Method Code (typically 9999). | ||
| If using RTPConnect, set SupplierCode to 1 and DistributorCode to the DisctributorCode being used by RTPConnect for Aspenware. | ||
| Set to the shipping fee product header code being used by the site (**This setting may not be used anymore) | ||
| If using AW Guest Check-out, set value to the IPTypeCode for the Guest Checkout Customer Type entry in the IPType table | ||
| If selling RTP Activities, these settings are used to determine if the RTP Activity lock has expired. So if the lock expires at 4:30:00 and it's set to 10 secs, then it will consider the lock is expired at 4:29:50 and try to get a new lock. This is to account for the amount of time after the order completes in AW but before it is processed into RTP by Unity. | ||
| Set Value to true. This allows a merged customer in RTP to get an updated Alternate ID Profile value. | ||
| Leave this Value set to 1000. This is used to lookup the RTP Sale Location Code for various purposes. | ||
| Define database settings. There are three connection strings.
| ||
| Define Aspenware Commerce Store settings. There can be more than one Store in this section if there are multiple Stores on the same Nop instance (i.e. Peak Mountain, Peak Highlands, Peak Golf, etc.) Define values as follows.
| ||