Once we move application to Production environment, it is become necessary to provide very tight security to BizTalk Administration Console as well as the users (Developers, Production Monitoring Users or Support Professionals) who need to monitor the application on regular basis.
To overcome the issue out-of-box Biztalk provides the role BizTalk Operator who will have limited access to BizTalk Administration Console, though there are some area where out-of-box biztalk functionality needs some alteration.
One instance is Default BizTalk Operators Group users can Start/Stop Receive Locations, Send Port and Orchestrations, To maintain high level of security some client require us not to provide any update access to these areas as well.
We can achieve this by revoking Execute Permissions from 'BTS_Operators' database role on following stored procedures of BizTalkMgmtDB database.
[bts_ReceiveLocation_Status_Update]
[bts_SendPort_Status_Update]
[bts_SendPortGroup_Status_Update]
[bts_Orchestration_Status_Update]
Hope this Helps!!!!
To overcome the issue out-of-box Biztalk provides the role BizTalk Operator who will have limited access to BizTalk Administration Console, though there are some area where out-of-box biztalk functionality needs some alteration.
One instance is Default BizTalk Operators Group users can Start/Stop Receive Locations, Send Port and Orchestrations, To maintain high level of security some client require us not to provide any update access to these areas as well.
We can achieve this by revoking Execute Permissions from 'BTS_Operators' database role on following stored procedures of BizTalkMgmtDB database.
[bts_ReceiveLocation_Status_Update]
[bts_SendPort_Status_Update]
[bts_SendPortGroup_Status_Update]
[bts_Orchestration_Status_Update]
Hope this Helps!!!!
No comments:
Post a Comment