Temporarily adding MID Server java wrapper properties for debugging, using via MID Profiles in the InstanceSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } ServiceNow support have traditionally relied on customers to log into the host server to make changes to the wrapper-override.conf file of MID Server installs, to enable properties to help with debugging. Since MID Server Profiles have become available for non-Containerized MID Servers in the Zurich version, these java properties can now be set from the instance. There is an extra wrapper configuration file named agent\conf\wrapper-profile-sync.conf, which overrides properties in the out-of-box wrapper.conf or manually edited wrapper-override.conf files. Note: If the MID Server is already using a Profile, then don't use these steps. This adds a whole new temporary Profile, and then removes it again, which can't be done if one already needs to be used. Warning: Only include the setting in the profile that you want to temporarily add, that don't already exist. Leaving other settings in may override the customer's existing settings with bad values. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } From Zurich. Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Steps are: Create the profile From the navigation, go to MID Server -> Profiles and Deployments -> MID Server ProfilesClick New, and on the new form fill in a good name and description, so anyone stumbing across this known why it was added. Right-click the header, and Save Once the profile is saved, the form will have several related lists, for various types of settings. Clear any extra configurations out of the profile. You need to do this to be sure that you'll not to override or change any existing configurations. You will see "url" has been automatically added. Delete that.If you had used the 'Create MID Profile' related link in the MID Server's form instead, you would have a lot more to delete. Add the debug properties to the profile In the MID Profile Wrapper Configs related list, click New.Enter the Name and Value of the property, and SubmitNote: This example would be directly equivalent to manually adding the following line to the end of wrapper-override.conf: wrapper.java.additional.201=-Djavax.net.debug=ssl:handshake Repeat this step for all the java properties you need to add. Set the profile on the MID Server record, and Sync it to the MID Server Navigate to MID Servers -> Server, then open the record for the MID ServerSet the form view to "Default", because this is the only one that has the Profile ID field (Problem TBC)Enter the Profile name in the Profile ID fieldImmediately this popup will appear:Confirm the '..leave other mid sepcific settings alone' strategy is selected.Tick 'Sync wrapper-override settings...'Tick 'Do you want to Auto restart...'And if you are sure that restarting the mid server now isn't going to cause problems, click Sync Profile. You should then see an ecc_queue output record is created for topic=SystemCommand and source=updateConfig, where the payload includes a mid_profile_id. That will cause config.xml to be edited to add the profile id.You also expect to see an ecc_queue output record created for topic=SystemCommand and source=wrapper_override_operation.If you don't see that (problem TBC): Open the MID Server Policy recordClick the 'Sync to MID servers' related link.You will see the same popup as above, than should be filled in as above. The MID Server will restart to apply the property to Java The agent log will confirm if the property was added and restart was triggered: INFO (Worker-Interactive:SystemCommand-e9ecf266fbf3f6d09d14fbee3eefdce7) [WrapperOverrideConfigManager:364] Changed properties saved to MID wrapper override file. Changes made: [{Added: wrapper.java.additional.201}]INFO (Worker-Interactive:SystemCommand-e9ecf266fbf3f6d09d14fbee3eefdce7) [WrapperOverrideOperationHandler:203] Wrapper override file modified.Triggering a mid restart. The agent\conf folder listing will confirm the wrapper-profile-sync.conf is updated, and a backup of the previous file created.Inspecting the file will show the property was added: Now do your debugging, reproduce, grab logs etc.Remove the profile from the MID Server: Open the MID Server formClear out the Profile ID fieldSaveExpect to see: and an ecc_queue output for topic=SystemCommand and source=updateConfig, that will cause config.xml to be edited to remove profile id. As of Australia Patch 0, the wrapper-profile-sync.conf file does not get cleared out, and remains in effect. (problem TBC)To workaround that, the wrapper-profile-sync.conf file needs reverting using the backup file. To do that: Insert a a new ecc_queue record, with fields set like this, to get the file names: agent: mid.server.<mid server name>topic: CommandName: dir conf\wrapper-profile-sync*.*queue: ouputstate: ready find the ecc_queue input for that output, to see what the filename of the backup file was.Insert a a new ecc_queue record, with fields set like this, to copy the backup over the live file. agent: mid.server.<mid server name>topic: CommandName: copy "conf\wrapper-profile-sync_<backup timestamp>.conf" conf\wrapper-profile_sync.confe.g. copy "conf\wrapper-profile-sync_2026-03-04T12_57_58.000+0000.conf" conf\wrapper-profile-sync.confYou will need to use the name of the backup file found with the dir command.queue: ouputstate: ready Restart the MID Server using the 'Restart MID' related link on the MID Server form. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Docs: MID Server Deployment and Auto-configuration - MID Server Profile The property used as the example:KB0717261 How to enable SSL debug on the mid server to troubleshoot any issues with SSL connections?