hi Carrie,
I am trying to see the feasibility of defining the PROFILE for the system ids like DBC,TDWM,Crashdumps,Systemfe,SysAdmin,LockLogShredder...etc.
As you said for DBC being a super-user we cannot control it via profile attributes. But i think for rest of the users we can define a profile and not sure if there are any limitations applicable.
Let us say, if I want to have every id's (including system ids) PARSING phase to be completed in PARSING only workload, I think I cannot have DBC to fall into that PARSING only workload becuase it donot have a profile. So it will fall into its own workload (we have one defined for dbc and tdwm). But for rest of the ids (tdwm/systemfe/crashdumps...) if i define a special PROFILE, then i can have them to get advantage of PARSING only workload. Just wanted to know if there are any do's and dont's for defining a profile for system ids (excluding DBC).
hi Carrie,
I am trying to see the feasibility of defining the PROFILE for the system ids like DBC,TDWM,Crashdumps,Systemfe,SysAdmin,LockLogShredder...etc.
As you said for DBC being a super-user we cannot control it via profile attributes. But i think for rest of the users we can define a profile and not sure if there are any limitations applicable.
Let us say, if I want to have every id's (including system ids) PARSING phase to be completed in PARSING only workload, I think I cannot have DBC to fall into that PARSING only workload becuase it donot have a profile. So it will fall into its own workload (we have one defined for dbc and tdwm). But for rest of the ids (tdwm/systemfe/crashdumps...) if i define a special PROFILE, then i can have them to get advantage of PARSING only workload. Just wanted to know if there are any do's and dont's for defining a profile for system ids (excluding DBC).