The Full Monty – Part 8 – BI Content

Previous blog, The Full Monty – Part 7 – Upgrade to SP6

Well, as we have got this far, after a successful upgrade to SP6, it seemed only natural to attempt to install BI Content.

Take a look at what BI Content already exists. You see very little.

Navigate to RSA1->BI Content (button).

There are six InfoAreas, that contain a limited amount of BI Content.

Naturally, you will have to download the BI Content from the Sap Market Place which is delivered as a Support Package. 

Nb: If your SAP User ID does not have the correct privilages, you will not be able to see these.

Downloads(tab)->SAP Support Packages(tab)->Support Packages and Patches – Entry by Application Group->SAP Content->BI Content->BI CONT->SAP NW 7.0 BI CONT ADDON 7.04->Support Packages 

Downloads(tab)->SAP Support Packages(tab)->Browse our Download Catalog->SAP Content->BI Content->BI CONT->SAP NW 7.0 BI CONT ADDON 7.04->Support Packages

Here are the BI Content files I downloaded.

• K-704IHINBICONT.SAR
• K-70401INBICONT.SAR
• K-70402INBICONT.SAR
• K-70403INBICONT.SAR
• K-70404INBICONT.SAR

I then logged on the the NSP, Client 000, as DDIC, put my “magic” break point in place (see previous blog – Upgrade to SP6) and then ran transaction SAINT, the Add-On Installation Tool, that can also be used other than the Support Package Manager (SPAM), for the likes of upgrading like this.

In the hope I could load them from where I downloaded them, I chose, Installation->Load Packages->From FrontEnd, and navigated to my files

But as I added the first, I got the following message, about the file being too large.

I chose “Yes”, and Boom ! It blew me right out of the NSP completely. I tried again. And so did it, boom!, again, blown out. So I had to resort to reading the online help, as it suggests, which of course, I did not have. But, I did remember doing this once upon a time.

I opened a DOS box, and used “sapcar.exe.” to manually extract the files. Below are the DOS prompts and command lines copied from the DOS box. Each file extraction task is separated by the file name in bold for you to be able to distingusish between the actions.

K-704IHINBICONT.SAR 

The command line I type... 

     C:sapfilesBIContent>C:sapfilessapcar.exe -xvf C:sapfilesBIContentK-704IHINBICONT.SAR

The prompt returned with the following information…

     SAPCAR: processing archive C:sapfilesBIContentK-704IHINBICONT.SAR (version 2.01)

     x EPS/in/CSR0120031469_0033010.PAT

     SAPCAR: 1 file(s) extracted

K-70401INBICONT.SAR

The command line I type… 

     C:sapfilesBIContent>C:sapfilessapcar.exe -xvf C:sapfilesBIContentK-70401INBICONT.SAR

The prompt returned with the following information... 

     SAPCAR: processing archive C:sapfilesBIContentK-70401INBICONT.SAR (version 2.01)

     x EPS/in/CSR0120031469_0033161.ATT

     x EPS/in/CSR0120031469_0033161.PAT

     SAPCAR: 2 file(s) extracted

K-70402INBICONT.SAR

The command line I type... 

     C:sapfilesBIContent>C:sapfilessapcar.exe -xvf C:sapfilesBIContentK-70402INBICONT.SAR

The prompt returned with the following information... 

     SAPCAR: processing archive C:sapfilesBIContentK-70402INBICONT.SAR (version 2.01)

     x EPS/in/CSN0120061532_0034803.ATT

     x EPS/in/CSN0120061532_0034803.PAT

     x EPS/in/CSN0120061532_0035746.ATT

     x EPS/in/CSN0120061532_0035746.PAT

     SAPCAR: 4 file(s) extracted

K-70403INBICONT.SAR

The command line I type... 

     C:sapfilesBIContent>C:sapfilessapcar.exe -xvf C:sapfilesBIContentK-70403INBICONT.SAR

The prompt returned with the following information...

     SAPCAR: processing archive C:sapfilesBIContentK-70403INBICONT.SAR (version 2.01)

     x EPS/in/CSR0120031469_0036967.ATT

     x EPS/in/CSR0120031469_0036967.PAT

     SAPCAR: 2 file(s) extracted

K-70404INBICONT.SAR

The command line I type... 

     C:sapfilesBIContent>C:sapfilessapcar.exe -xvf C:sapfilesBIContentK-70404INBICONT.SAR

The prompt returned with the following information...

     SAPCAR: processing archive C:sapfilesBIContentK-70404INBICONT.SAR (version 2.01)

     x EPS/in/CSN0120061532_0039170.ATT

     x EPS/in/CSN0120061532_0039170.PAT

     SAPCAR: 2 file(s) extracted

I looked a little closer at the returned messages and noticed how all the extracted files were added to a newly created location “EPSin”, under where the files were my original files were located – “C:sapfilesBIContent”

I copied all of the above files, into the NSP’s “EPS/in” directory – “C:usrsap     ransEPSin”. There were a number of files already existing, from previous Service Package upgrades. As I said, I simply copied the BI Content recently unpacked files from “C:sapfilesBIContentEPSin” into the NSP directory “C:usrsap     ransEPSin”.

Once again, I logged in as DDIC, client 000, with the “magic” break point in place. Then commenced to SAINT

“Start”

Selected the only BI_CONT entry here, and “Continue”

In the BI_CONT dropdown, select the entry “SAPK-70404INBICONT”, and “Continue

“Continue”, and say “No”, to the next “…Modification Adjustment Transports…” message.

This next screen was an unexpected suprise

Needless to say, I had to use the “SAP Note” button, to navigate to the SAP Note, and spent a few minutes trying to find the Password, amongst the text and information. As you can see above, I found it, entered it in, then proceeded with the “Tick” button.

Now I knew I was getting near. I selected “Start Options”

Chose “Start in background Immediately”

Finally, the “Tick”.

The next screen is SAINT again, only in display mode, as it says, because the import/upgrade, is now underway.

You can use the “Refresh” button to monitor progress.

The process took over 6 hours. You can monitor it’s progress with the file “C:usrsap     ranslogALOG1021.NSP”.

The next morning I switched on the machine and started up the NSP, logging on as DDIC in client 000, to see the fallout.

No problem! No fallout, just get the splash screen. So far so good.

I fire up SPAM, and it says it is locked by SAINT, so I call SAINT.

As you can see above, I had to press “Finish”, so I did

I can see BI_CONT, but I wanted more, so I call SPAM and navigated to the “Package Level” (button) and again I now see “BI_CONT” (Business Intelligence Content) as an installed Package.

One final test, Log out of Client 000, and in to Client 001, as BCUSER, to run transaction RSA1->BI Content

A stark difference to what we had earlier. BI Content, now all in.

Update 4.6.2010 I picked up remaining to BI Content Support Packages, 5 & 6, and ran them both together, using the Support Package Manager (SPAM), with my “magic” break point in place. Resulting after about and hour and a half, a newly packaged NSP.

Continue to my next blog…

The Full Monty – Part 9 – The CE2 Install