Can I use the embedded SQL Anywhere in BI Platform to create Data Services Repositories?

[former_member421392]

Hello community.

A customer acquired SAP Businessobjects Enterprise Professional Edition. My question is: under this license scheme is it possible to use the embedded SQL Anywhere in the BI Platform to create the Databases for the Data Integrator repositories without incurring in a license infringement?

[former_member240871]

I grabbed this by running dblic ./dbeng17.lic from the sqlanywhere BIN64 directory)\

SQL Anywhere Server Licensing Utility Version 17.0.8.4103 License read successfully.
OEM Edition
Add-on: High Availability
Add-on: In-Memory mode
Add-on: Scale-out Nodes
Licensed nodes: 1

Odds are no. SQL Anywhere installed with BI Platform is under an OEM license which is likely restricted in some way to BOBJ.

KBA 2568027 has some info on licensing, although it's not super detailed. https://launchpad.support.sap.com/#/notes/2568027

[Sawa_Ito]

Which version of BI Platform did you check?

[former_member240871]

4.2 SP06 - There's a second license key file in the same directory, dbsrv17.lic which has this output as well:

SQL Anywhere Server Licensing Utility Version 17.0.8.4103

License read successfully.
OEM Edition

Add-on: High Availability
Add-on: In-Memory mode
Add-on: Scale-out Nodes
Licensed nodes: 100000
User: SAP
Company: SAP IT

[Sawa_Ito]

Thank you.
The reason why I asked this is that there was a problem in BI/IPS 4.1 SP7, in which the number of node (connection) of SQL Anywhere Server (dbsrv) was wrongly set to be one, which caused problem for DS users to concurrently connect to DS.
(At that time, from the Data Services installation guide the SQL Anywhere bundled with IPS can be used as both CMS database and the Data Services repository database. I have not checked it, but I guess it is not changed.)

To solve the problem following note was created.

2364173 - The instance of SQL Anywhere that is installed with Data Services can only accept one database connection
https://launchpad.support.sap.com/#/notes/2364173

It seems this version does not have the same problem.