BI 4 LCM using CTS+ on SolMan, Simplified?
I recently was tasked with setting up CTS+ for a BoE/BOBJ/BI 4.0 system. I came across the following documentation which was extremely useful in setting up the majority of the infrastructure.
I met the following pre-reqs:
- CTS_PLUG 2.0 SP08
- BI 4.0 higher than Feature Pack 3
My setup was with a Solution Manager 7.1 system and two sandbox systems for BI 4.0 one had some data/reports from an actual BI 4 system and the second BI 4 system was a blank slate; the test consisting of obtaining a transport number and a successful import of the transport for BI 4 and Solution Manager’s TMS.
SOA Manager screenshot for the transport settings, the guide has you put in /001/export_cts_ws1; I instead chose to do it without the /001 part:
The next issue I ran into, was needing to confirm the TMS config for the BI systems; I have found these settings to work best for my situation:
TRANSDIR will be filled out by the system, along with the COMMUNICATION_SYSTEM which will be your SolMan SID ## The above is the “Development” system.
Below is the “Production” system:
Next comes the Application Types and Deployment methods, wasn’t 100% what I needed to have configured as the Deployment method is unique for each Non-ABAP System!
The Application Type is populated by a previous step, and is accessed at the System Overview view, under the ‘Extras’ menu.
So the Deploy method being a drop down is the easy part as that is the EJB selection. The URI/user/password are all unique values and depend upon how the BI system is setup:
Deploy URI: http://<HOSTNAME.FQDN>/BOE/LCM/CTSServlet?&cmsName=<HOSTNAME.FQDN>:6400&authType=secSAPR3 (secSAPR3 can be changed to secEnterprise)
User: Will vary depending on the authType=secSAPR3 or secEnterprise (Critical info that must match BD1)
Password: Will vary due to the username
Now my opinion is to use secEnterprise, if the SAP system that handles the authorizations then you will also have transport issues; may not be a problem for a Dev system, but a QA or Prod system and having workflow handling your transports could cause some issues down the road.
This is probably where a lot of my troubleshooting took place as the final piece of the puzzle turned out to be an authorization issue to Solution Manager. The below error for my situation was actually a false positive!
Now let me mention the following 2 notes as this may not be a false positive for everyone:
The following is useful for those running BI 4.0 Feature Pack 3 or higher:
Under the Web Service Settings (aka CTS+ login) you have 3 fields to populate:
- Web Service URL: http://<HOSTNAME.FQDN>:80<NN>/EXPORT_CTS_WS1 ( Note the case sensitive /EXPORT_CTS_WS1)
- User: This user needs to exist on SolMan, the guide uses BOPM_Proxy
- Password: Password for the user
It was at this section that I had my authorization error that led to the false positive error, I was able to get things moving along by assigning SAP_ALL to the BOPM_Proxy user; I also understand this is not a desired result, and is something I am working on with the assistance of the security team.
Now the ‘BW Systems’ option, Im not entirely sure what needs to be done here; however I discovered a strange thing without any ‘BW System’ defined your BI developers will notify you about a second false positive!
Within the LCM/Promotion Mgmt when you add objects for the transport you will have the following buttons:
If you have not specified the ‘BW Systems’ and you click Add & Close you receive the following error:
The fix, supply a ABAP system under the ‘BW Systems’; not sure if it has to be a BW system; and interesting enough the objects you are adding to the promotion job…are in the job, wasted a few hours on this error!
Now be warned, when you put in the info for a ‘BW Systems’ it will place a .properties file at the host level and EVERYTHING within the file is plain text including the password!
And the final important gotcha that I ran into is the LCM_SOURCE_CMS_SID_MAPPING.properties file!
This file that you need to create manually is what controls the 3 character system that TMS utilizes; so if you setup your Development BI system as BD1, this file needs to have BD1 as the “<SID>” so your transport request starts with a “BD1K”.
There are only 3 lines needed for this mapping file: