Pages

Subscribe:

Wednesday, 29 February 2012

Business Objects Content Management planning

Hi BOOglers,
Let us resume with Administration track once again with Content management planning in Business Objects. Hope this is going to be more interesting and helpful for the Administrators to start up with.
Content management plan is a collection of procedures used to manage Business objects work flow in a collaborative and manageable environment. This ensures who needs access to what. While planning for Business Objects enterprise system appropriate content management planning is an important factor. Because of lack of expertise and time we always end up with BOE environment which is not structured properly, as a result BOE environment will become more difficult to manage and maintain.
Below are simple measures to consider in order plan for our BI content.
  • Easy to understand the hierarchy and secure implementation
  • Ensure users only accessing documents which they interested and authorized to.
  • Efficient structure so users are able to search the info they need easily
  • Easy access to information in the system will increase effectiveness of using the system.
Points to be consider for the Content management Planning
1. Creating a folder structure and organizing objects
As a first and foremost step we need to segregate the BI content according to users who is going to consume the information. This will enable us to decide the folder hierarchy of the system.
For example, for set of reports to Marketing department, we will manage them in the Marketing parent folder. Then we have a subfolder called Marketing- Americas or Marketing-Asia Pacific where reports can further be separated.
2. Organize users by creating a Group/User structure
Now we need to organize user group structure that will allow access to BI content. This will be similar to the folder structure, in our example we will be having a Marketing group each further categorized basd on the region.
3. Set access levels for folders and objects
Next we need to establish the security access levels for folders and objects contained in our group/user structure. This is extremely critical as we may risk in setting inappropriate security access levels for our users. Determining the needs of our users will help us establish who needs access to what folders and objects within the system. For example only users of the Marketinggroup can access the Marketing folder based on their functional roles.
Custom access levels created for each functional user group is depicted as below.
And finally this is how security is applied on Folder at Group level.
4. Creating corporate categories and assigning objects
The advantage of categories is that it will help the uses to search and access the reports that are appropriate to them. This can be configured according to uses requirement.
For example, the Marketing department user search for reports that are specific to vendor evaluation,
Even if the vendor related reports managed across different folders, we can create a separate category called Vendor management and group the corresponding reports in the Vendor management category. As a result the user not necessarily needs to go to every folder and search for the required report. They can simply access the category with which they authorized to access with.
In the below screen though the reports Marketing Dashboard and Sales Dashboard physically exist in Marketing and Sales folders respectively, still they can be accessed from Vendor  Management category.
The above are the initial steps that we can take to create a planned content management system with which we can end up with success.
I look forward to your inputs and feedback. Thanks for reading!

Tuesday, 14 February 2012

Business Objects Mobile – Configuration

Hi BOOglers,
This is the continuation of my previous blog Business Objects Architecture and Deployment. Hope you all eager to know about the BO Mobile configuration. Let us proceed further
Environment & Product versions used:
  • Operating System: Windows Server 2008 R2
  • BOE XI4.0 with BOBJ MOBILE XI4.0
  • BlackBerry Email & MDS Simulator
  • BlackBerry Device simulator
The BO Mobile server was installed on the same machine that hosted the BOE server.
The BlackBerry Email MDS Simulator & BlackBerry device simulator also Installed in the same machine. This architecture is depicted as below.
Installed Components and CCM:
Once we done with all the above, we can start with the Mobile Server configuration.
Mobile Server configuration
Launch Mobile Server Configuration Tool from Start menu. Select Blackberry BES Deployment as we are going to configure with BES simulator.
Application Installation in Mobile Client
Go to the below URL, provided you have already deployed the MobileOTA14.war file in Web Application Server. Please note BI will be replaced with your CMS Server name. You will get the screen like below
http://BI:8080/MobileOTA14/OTADeploy
Now try to access the URL from Device simulator.
Once Application is downloaded,configure with your credentials and access it from the mobile device.
Finally we got it in mobile. Let us compare this with desktop based GUI.
Mobile Vs Web browser comparison
This is all about BO Mobile configuration. Hope you feel it so easy to deploy and configure.
If you have any questions, or if you want to share your experience, feel free to leave a comment!
Happy Blogging!

Friday, 10 February 2012

Business Objects Mobile – Architecture and Deployment

Hello All,
As a continuation of my previous blog, we are going to see more in detail about BO Mobile Architecture, Deployment scenarios, Server side and client side requirements in this blog.
The diagram below shows Mobile Installation on top of Business Objects Enterprise Framework
And the Business Objects Mobile Architecture will be like
Three deployment scenarios are supported for SAP Business Objects Mobile. You can choose to deploy based on your User community.
  • BlackBerry devices registered on a corporate BlackBerry Enterprise Server (BES)
  • Non-BlackBerry devices and/or BlackBerry devices not registered on a corporate BES. This requires a proxy server or firewall to ensure security.
  • User population that includes BlackBerry devices registered on the BES and other devices. This requires a BES and a proxy server or firewall.
Based on the above deployment scenarios the common architecture of BO Mobile would be like
Server side requirements
The following components need to be deployed on top of SAP Business Objects Enterprise Installation.
  • The Mobile server composed of an authentication server (VAS) and a processing server (VMS).
  • A mobile database that logs the user activity and provides information on synchronization of data between the SAP Business Objects Enterprise server and the mobile devices.
  • A BlackBerry Enterprise Server (BES), if you are deploying the application to BlackBerry device users (Deployment type 1).
  • A proxy server, if your deployment to BlackBerry devices does not include a BES server or if your deployment includes non-BlackBerry devices (Deployment type 2 and 3).
  • To deploy client application to devices through OTA provisioning, you need to install and deploy the OTA web application, delivered with SAP Business Objects mobile, on a web application server.
Client side requirements
Based on deployment scenario, SAP Business Objects mobile application can be delivered to users via
  • Over-The-Air to BlackBerry devices using the push capability in the BlackBerry Enterprise Server.
  • Over-The-Air (OTA) via a secured web site page. This requires you to deploy the OTA web application delivered with SAP Business Objects Mobile to a secured web application server.
  • Manually on each device using the client desktop application supplied by device manufacturer.
I Hope this blog gives a good understanding on Business Objects Mobile architecture and deployment.
In our next blog we will see configuration of BO Mobile using Blackberry simulators.
Keep reading!

Friday, 3 February 2012

Business Objects Mobile – Introduction

Hello BOgglers,
Just a change from series of BO Administration series to emerging trends in SAP Business Objects.SAP BO Mobile is going to be the topic of discussion in my upcoming blogs starting from this.
The shift from a wired world to a wireless world of connectivity with the advantage of smart phones and handheld devices has lead to a new era of mobile computing, especially in the field of BI. BO Mobile allows to access favorite BI reports, metrics and right-time data with a single click from a mobile device with the following advantages
  • Make informed decisions with instant access to personalized information on the move, can be alerted about changes to critical business data instantly.
  • Leverage existing BI investments & skills to quickly reach mobile users.
  • Users can intuitively access familiar reports without a need for additional training.
Devices Supportability
BO Mobile supports broad range of mobile devices including BlackBerry, Windows Mobile, Symbian OS and any J2ME 2.0-compatible devices.
Supported document types
  • Web Intelligence documents
  • Crystal Reports documents
  • Limited gauge analytics (speedometers, barometers and thermometers)
Functionalities Supported
  • Save documents locally and consult them offline, to mitigate network interruptions and minimize communication costs.
  • Receive alerts when a document is modified, a condition is met or a schedule is run.
  • Follow-up actions by clicking on report cells to launch an SMS, phone call or email.
  • Set up a default document that opens automatically whenever log into application.
  • Refresh reports to retrieve the most up-to-date data.
  • View results using zoom and navigational shortcuts.
  • Navigate to related documents via hyperlinks on reports.
  • Drill on results to analyze detailed or summary data.
  • Track data changes via customizable highlighting set up by the document creator.
Target Audience
Information executives: Users who needs to know a few high-risk KPIs at the right time, no matter where they are. A business case for this could be a sudden fall in sales or inventory levels brought to the attention of the respective director.
Field workers: Users of this segment work in the field and need specific information at specific times. A sales representative, while finding an unexpected opportunity, can browse for required historic information such as price negotiation, contract tenure to give immediate feedback to the customer.
Business analysts: Business analysts need a few strategic KPIs in addition to static reports.
Clerical member staff: This people occasionally need reports while they are on the move.
Limitations
  • BO Mobile is not guaranteed to work on all mobile devices and operating systems.
  • Report data sets can be large and can theoretically saturate available device memory. The unsatisfactory display of large data sets can be mitigated by designing smaller report views.
We will see more in detail about Mobile Architecture and installation and configuration in upcoming blogs.
Thanks for reading! Happy Blogging!  Read More about  Business Objects