• Business Objects XI 4.0 will be made available in the SAP Marketplace come October. Customers who would like to use it in a Production environment will need to request permission from SAP.
• Desktop Intelligence will not be included in this release – https://wiki.wdf.sap.corp/wiki/display/globalregions/DeskI+End+of+life
  The only way to get Desktop Intellignence reports onto XI 4.0, is to first convert them to Web Intelligence in XI 3.1 or use the Report Conversion Tool.
• Web Intelligence will now be called Interactive Analysis.
• Business Objects XI 4.0 will only be a 64-bit release.
• Business Objects XI 4.0 will use Tomcat 6 with Java 1.6.
• A single WAR file for InfoView and CMC.
• Timeout settings are now accessible in one place and will include a timeout warning.

If there is a requirement to add additional components to an existing deployment, be wary of the build version of the newly added component(s) if you are running Service/FixPack(s) ontop of a base installation. As BusinessObjects will install these new features from the base installation, hence the Service/FixPack will need to be reapplied.

For example:

Scenario: You have an existing server installation of BusinessObjects Enterprise XI R2. This server was built by installing BOE XI R2 Service Pack 4 (Integrated – Base Installation) + Service Pack 6.

Requirement: You would like to add a Web Intelligence Report Server, since it was not part of the original installation you will need to modify the existing.

Process:

1. Open Control Panel, and choose Add or Remove Programs
2. Click on BusinessObjects Enterprise XI R2 and choose [Change]. Note: You will notice that you are unable to “Change” the Service Pack 6 entry.
3. Select the additional feature and follow the normal installation process

Once the installation is complete, check the build version of the newly added feature and compare to those which have had Service Pack 6 applied. You will notice they are out of sync.

Unfortunately, the only way to remedy the situation is by reapplying any Service/FixPack(s) that have been installed over the base installation (i.e. Uninstall/Reinstall).

Note: These steps apply to Business Objects XI Release 2.

File to be modified:
_logon.jsp

Directory:
D:\Program Files\Business Objects\Tomcat\webapps\businessobjects\enterprise115\desktoplaunch\InfoView\logon

Servers:
Web Application Servers

Steps:

1. Stop Apache Tomcat
2. Find the code below (within _logon.jsp):

<td align=”left”>

<c:choose>
<c:when test=”${logonForm.afInstalled}”>
<%– if af is installed disable the CMS edit box –%>
<html:text disabled=”true” styleClass=”textfield” property=”cms” style=”width:200px” styleId=”apsTextEdit” onkeydown=”keydownfn(event)”/>
</c:when>
<c:otherwise>
<html:text styleClass=”textfield” property=”cms” style=”width:200px” styleId=”apsTextEdit”/>
</c:otherwise>
</c:choose>
</td>

3. Insert disabled=”true” into the section shown below:

<td align=”left”>
<c:choose>
<c:when test=”${logonForm.afInstalled}”>
<%– if af is installed disable the CMS edit box –%>
<html:text disabled=”true” styleClass=”textfield” property=”cms” style=”width:200px” styleId=”apsTextEdit”/>
</c:when>
<c:otherwise>
<html:text disabled=”true” styleClass=”textfield” property=”cms” style=”width:200px” styleId=”apsTextEdit” onkeydown=”keydownfn(event)”/>
</c:otherwise>
</c:choose>
</td>



4. Save _logon.jsp
5. Restart the Apache Tomcat.

 Note: These steps apply to Business Objects XI Release 2.

1. Log on to the Management Tier

2. Stop the Central Management Server

3. Navigate to Central Management Server > Properties > Configuration > Change Cluster Name (e.g. BOENV)

4. Log on to the Web Tier

5. Stop Apache Tomcat

6. Navigate to Program Files\Business Objects\Tomcat\webapps\businessobjects\enterprise115\desktoplaunch\WEB-INF\

7. Open web.xml in Notepad

8. Jump to the section shown below (search for ‘cms.default’) and update accordingly

<context-param>
<param-name>cms.default</param-name>
<param-value>@BOENV</param-value>
</context-param>

9. Jump to the section shown below and update accordingly (boenvserver is the name of the server the CMS resides on and @BOENV is the name of the cluster)

<context-param>
<param-name>cms.clusters</param-name>
<param-value>@BOENV</param-value>
</context-param>
<context-param>
<param-name>cms.clusters.BOENV</param-name>
<param-value>boenvserver:6400</param-value>
</context-param>

Before:

After:

10. Save web.xml

11. Navigate to D:\Program Files\Business Objects\Tomcat\webapps\businessobjects\WEB-INF

12. Open web.xml in Notepad

13. Jump to the section shown below (search for ‘connection.cms’) and update accordingly

<context-param>
<param-name>connection.cms</param-name>
<param-value>@BOENV</param-value>
<description>This is the name of the CMS that you would like your application(s) to connect to. WCS_NAME_SERVER</description>
</context-param>

14. Save.web.xml

15. Restart Apache Tomcat & Central Management Server

16. Delete Cookies from Browser (e.g. Internet Explorer: Tools > Internet Options… > [Delete Cookies...])

References:

SAP Note: 1274198
SAP Note: 1218472

For a Single Client Tool:
“<Path to setup.exe> /qn+ REBOOT=ReallySuppress CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH=”Client” ADDLOCAL=”Clients,ClientFeatureName”

For Multiple Client Tools:
“<Path to setup.exe> /qn+ REBOOT=ReallySuppress CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH=”Client” ADDLOCAL=”Clients,ClientFeatureName1,ClientFeatureName2,ClientFeatureName3″

Example: Universe Designer
setup.exe /qn /qb REBOOT=ReallySuppress CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH=”Client” ADDLOCAL=”Clients,Designer”

Windows Installer Command-Line Options

/qn - Quiet display option. The installer runs an installation without displaying a user interface. No prompts, messages, or dialog boxes are displayed to the user. The user cannot cancel the installation.

/qb – Basic User Interface

REBOOT=ReallySuppress - Never restart option. The installer never restarts the computer after the installation.

ADDLOCAL - List of features that are delimited by commas, and are to be installed locally.

For further information regarding Windows Installer Command-Line Options

http://msdn.microsoft.com/en-us/library/aa372024%28VS.85%29.aspx
http://msdn.microsoft.com/en-us/library/aa367988%28VS.85%29.aspx

Reference: SAP Note 1220125

Absolute Hyperlink using Document Name

http://<server name>:8080/businessobjects/enterprise115/desktoplaunch/opendoc/openDocument.jsp?sDocName=Document%20Name

Relative Hyperlink using Document Name

../../opendoc/openDocument.jsp?sDocName=Document%20Name

Absolute Hyperlink using Document ID

http://<server name>:8080/businessobjects/enterprise115/desktoplaunch/opendoc/openDocument.jsp?iDocID=1234

Relative Hyperlink using Document ID

../../opendoc/openDocument.jsp?iDocID=1234

Hyperlink that specifies Output Format (H = HTML, P = PDF, E = Excel)

http://<server name>:8080/businessobjects/enterprise115/desktoplaunch/opendoc/openDocument.jsp?iDocID=1234&sOutputFormat=P

I strongly recommend utilising hyperlinks with a relative URL path as opposed to defining the path in full (absolute).

The advantages of a relative reference are…

• As reports (hyperlinks) are migrated from one environment to another, the hyperlinks will not break as the URL path is relative to the server it is running on at the time, and the server name is never explicitly defined.
• Turning SSL on or off (i.e. switching between HTTP or HTTPS) will not break the URL.
• Changing the Port number the website runs from (i.e. 8080 or 8443) will also not break the URL.

Application: Central Management Console

Navigate to: Home > Servers > Web Intelligence Report Server > Properties

Description: The Connection Time Out property dictates the number of minutes before an idle connection to the Web Intelligence Report Server will be closed.

Note: The value should be equal to what is set for the –RequestTimeout switch (i.e. CORBA timeout).

Application: Central Configuration Manager

Navigate to: CCM > Web Intelligence Report Server > Properties > Command

Description: The -RequestTimeout switch modifies the default CORBA timeout.

Note: When a scheduled Web Intelligence document runs for more than the set CORBA timeout, the following error message appears: “Transport Error, Communication Failure”.

Add “-RequestTimeout nnn” to its command line (where “nnn” is the duration in milliseconds you want the timeout to be). For example, -requesttimeout 3600000 sets the timeout to 60 minutes.

Example: “\\HOST\C$\Program Files\Business Objects\BusinessObjects Enterprise 11.5\win32_x86\wireportserver.exe” -service -name host.domain.com.Web_IntelligenceReportServer(5) -ns @host.domain.com -requestTimeout 3600000  -restart

Application: Central Configuration Manager

Navigate to: CCM > Web Intelligence Job Server > Properties > Command

Description: The –cdzReqTimeoutMs switch modifies the default Cadenza Request Timeout.

Note: The value should be equal to what is set for the –RequestTimeout switch (i.e. CORBA timeout).

Example: “\\HOST\C$\Program Files\Business Objects\BusinessObjects Enterprise 11.5\win32_x86\jobserver.exe” -service -name host.domain.com.jobserver -ns  @host.domain.com -requestTimeout 3600000  -  objectType CrystalEnterprise.Webi -lib procwebi -jsTypeDescription “WebIntelligence Job Server” -cdzReqTimeoutMs 3600000  -restart

Application: Designer

Navigate to: File > Parameters > Controls

Description: The Limit execution time to setting can be used to limit how long the SQL query is allowed to execute.

Note: This setting may have adverse effects on reports that contain multiple queries if the execution time is split evenly.

If we tried to Modify the report, the same initial error message would appear followed by a second: “An internal error occurred while calling the ‘getDocumentInfosMDP’ API. (Error: WIS 30270)”.

Further investigation revealed the physical WID file kept within the FileStore was of 0 KB in size. A case was raised with SAP/BO Support and the conclusion was that the report had somehow become corrupt and needed to be rebuilt (unfortunately for the end-user, there was no working copy in any of the other environments to migrate an instance from).

While this was not the ideal outcome, the engineer assigned to our case did supply us with the following interesting article which may be of interest to Business Objects users.

Why do files become corrupt in the InfoStore

Corruption generally occurs when the information stored on your computer’s hard drive or on diskettes becomes damaged. Improperly shutting down the computer, general protection faults, software conflicts, and voltage fluctuations are typical causes of file damage. In circumstances where a hard disk is not regularly maintained using Windows utilities (such as ScanDisk or Disk Defragmenter), files can lose integrity and become cross-linked, a situation where two or more files occupy the same physical space on the hard disk.

Each file will have its own type of formatting and control characters. WinWord has lots of control characters put in place as an example. So. If at any point any of the control characters are missing or have been changed to something else, file corruption happens most of the file viruses do this king of thing

What causes corruption?

In case of databases, one possibility of file corruption could be because of lack of synchronization between multiple processes trying to update one file. Usually Semaphores and locks will be used for synchronization between processes to access files.

For Example let’s say Process A has access to File F and the time slice is complete for the Process A then, Process B takes over and it also wants to update the same File F now, if Process A did not put a lock on a file, then, Process B will have full access to it. If Process A is in the middle of its updation and Process B has taken over, then, there is fair chance that the Process B starts updating the file and when Process A comes back to execute, it will start from wherever it was when its time slice was given. This is one reason for database corruption.

There can be several other reasons. But, mostly it is synchronization issues (in case of Database/File access). Another possibility, as I said before is because of Viruses corrupting the files. Usually, the software written should be efficient enough to handle synchronization.

Corruption of universe and objects may occur for a variety of reason. When the universe is stored on the PC, it is stored as an .unv file. When it is stored in the repository, it is broken up into relational definitions and rows in various tables – i.e. – the select statement is stored in one table, the object name for that select statement in another.   When you re-import the universe, it essentially rebuilds the .unv file.

When your customer exports/imports the universe and the objects. There is a process where the tool that do the format conversion from type –Universe and Objects – to the type suitable for storing in the table. Typically, when users may shut off their machines without closing down their applications, meaning apps, documents and files are closed down properly, due to power breakdown and voltage fluctuations ultimately causing said files and objects become corrupt.

Step 1. Verify that the Java SDK is installed and its location is in your PATH environment variable. If you are able to execute the jar command, and receive usage information on the command, proceed to the next step. If you receive an error message, install the JAVA SDK and add its location to your PATH.

Verify Java SDK is installed.

Java SDK location in the PATH environment variable.

Execute the jar command and receive usage information.

Step 2. Stop the Web application server on the machine where desktop.war is deployed.

Stop the Web Application Server (Apache Tomcat)

Step 3. Extract the web.xml file from the directory where desktop.war is deployed.

jar -xvf desktop.war WEB-INF/web.xml

Step 4. Open web.xml in a text editor like Notepad and search for the following section:

<session-config>

<session-timeout>20</session-timeout>

</session-config>

Step 5. Change the value between <session-timeout> to the number of minutes you require for the session to timeout.

Step 6. Save web.xml.

Step 7. Update the desktop.war with the modified web.xml file. Use the following command:

jar -uvf desktop.war WEB-INF/web.xml

Step 8. Restart you web application server and redeploy desktop.war.

Note: You don’t need to redeploy desktop.war if you edited the web.xml file from the deployed location. Restarting your web application server will suffice.

Step 1. Verify that the Java SDK is installed and its location is in your PATH environment variable. If you are able to execute the jar command, and receive usage information on the command, proceed to the next step. If you receive an error message, install the JAVA SDK and add its location to your PATH.

Verify Java SDK is installed.

Java SDK location in the PATH environment variable.

Execute the jar command and receive usage information.

Step 2. Stop the Web application server on the machine where webcompadapter.war is deployed.

Stop the Web Application Server (Apache Tomcat)

Step 3. Extract the web.xml file from the directory where webcompadapter.war is deployed.

jar -xvf webcompadapter.war WEB-INF/web.xml

Step 4. Open web.xml in a text editor like Notepad and search for the following section:

<session-config>

<session-timeout>20</session-timeout>

</session-config>

Step 5. Change the value between <session-timeout> to the number of minutes you require for the session to timeout.

Step 6. Save web.xml.

Step 7. Update the webcompadapter.war with the modified web.xml file. Use the following command:

jar -uvf webcompadapter.war WEB-INF/web.xml

Step 8. Restart you web application server and redeploy webcompadapter.war.