![Sap Bods 4.2 Administrator Guide Sap Bods 4.2 Administrator Guide](https://blogs.sap.com/wp-content/uploads/2018/03/image004.png)
Disable Unused User Accounts: a good security measure to put in place.Do not use Generic User Accounts: each person should have a real named account.You don’t want to be non-compliant with SAP otherwise it’ll be very expensive for you. → For more good practices on rights management and security, click here. View & Refresh: instead of allowing a user to review, refresh, and schedule, you can deny their permission to schedule.View Top Level Folder: when someone logs into SAP BusinessObjects for the first time they do not even see folders, only the top-level.I recommend you create Access Levels instead of going in the “Advanced” menu, for example: Add users to groups then assign permissions on the folders to the group. The best strategy is to make sure nobody has permissions then you give permissions when necessary. When you build your security model, never use DENY - if you don’t want someone to access something just don’t give them permission in the first place.
#Sap Bods 4.2 Administrator Guide install
If you do want to clear up space, SAP has just released the ONE Uninstaller - this is a safe way to uninstall old versions and it allows you to save disk space and more importantly, the next time you install a patch it’ll be installed a lot faster. Some of you may want to manually uninstall a service pack but this brings a lot of risk with it. I highly recommend to not go and manually delete InstallData as it will certainly cause serious problems. InstallData holds all the old backups you’ve installed over the years. The recycle bin also doesn’t back-up content if it gets corrupted, once it’s corrupted you cannot recover it as it is not a deleted object. Also, files are kept for 30 days by default but you can change this in the settings. For example, if you delete a user, you will lose the personal content and the user’s inboxes. I think it’s great but it doesn’t back-up everything. The recycle bin in SAP BusinessObjects is not a backup solution. Do Not Use The Recycle Bin As A Backup Solution
![Sap Bods 4.2 Administrator Guide Sap Bods 4.2 Administrator Guide](https://image.slidesharecdn.com/sbo401dsdesigneren-131213054333-phpapp02/95/sap-bods-designer-pdf-314-1024.jpg)
#Sap Bods 4.2 Administrator Guide license
You’ll need to know them at least for the following: Administrator Account, System and Audit Databases, Service Accounts, Cluster Key (required even if a single node and is given when you first install SAP BusinessObjects) and License Keys - can you remember all of them? 27. When you patch SAP BusinessObjects you will need to use the admin account and when you restore/backup databases you will need to know the credentials. → Get 360Plus to maintain your platform integrity. Tomcat configuration files and JAVA options, for example, need to be documented, it’s not enough to just have them backed-up because when you move from BI 4.2 to BI 4.3 these files will be gone. If you don’t back up the following you won’t be able to fully recover: If there’s no email on your account, the email notification won’t go anywhere. However, do make sure that the notification configuration is enabled in the settings. You have monitoring in SAP BusinessObjects and there are two watchers already by default for the disk space. Enable Disk Space Monitoring and Notification Make sure you have enough disk space : especially for temporary files when viewing WebIs and scheduling them, and every time you install patches and filestore (which will continually increase over time). This will allow you to then audit events of which administrators did what. The administrator account is good when you need to install a patch or control the administrative side but please limit the use as much as possible and use your own named account. I’ve got 16 more Business Objects tips and tricks on the administration and security side. If you’re motivated enough and reached this section we’re nearly there.