If your question is how to add debug level log into your syncmapping pattern, please read Log functions - BMC Discovery 11.3 - BMC Documentation and check examples into TKU patterns (for example in CMDB.Host_ComputerSystem).
These logs will be added to tw_svc_cmdbsync_transformer.log file. Read Changing log levels at runtime - BMC Discovery 11.3 - BMC Documentation and Contents of the logs - BMC Discovery 11.3 - BMC Documentation
3 of 3 people found this helpful
If you want to easily see your log messages, do not use log.debug! The only way to see those messages is to put the whole of CMDB sync into debug log mode, and then your messages will be drowned out in loads of other debug logging. For your own messages during development, use log.info or even log.warn or error, just so your messages stand out.
If you don't have any CMDB connections, then the syncmappings will not execute at all. You won't see any log messages from them until you add a CMDB connection. Alternatively, you can do a CMDB sync preview in the UI, which causes the mappings to execute even without a connection defined.
Thankyou for the info. It helped alot
mapping from Host_ComputerSystem.host where name = 'test' as host
traverse ElementWithDetail:SupportDetail:OSDetail:SupportDetail as ossupdetails
for each ossupdetails do
computersystem := Host_ComputerSystem.computersystem;
computersystem.BR_EndOfExtendedSupport_Date := '2024-06-28';
computersystem.BR_EndOfLife_Date := ossupdetails.retirement_date;
for this I am getting
ERROR (120007): Class Manager system error occurred during processing.; java.lang.ClassCastException (120007)
is it something that I need to cast the datatype
This is an AR error that I never saw. Could you provide the full stack trace, likely visible in tw_cmdbsync_exporter.log.
What are the data type of BR_EndOfExtendedSupport_Date and BR_EndOfLife_Date? You possibly feed these attributes with incorrect values.
is there any function to convert datetime to string
Is it fixed? if yes, then what was the fix?
1 of 1 people found this helpful
Is what fixed? It is not a defect. The custom syncmapping was passing a type which did not mach the custom fields.