Error trying to connect to Oracle model via Cloud

[Andre Lalonde]

I get the following error trying to connect to an Oracle model using the Cloud Service:

Cloud Services: Server Error - There is no database manager configured for the requested repository      

The cloud service was installed with all defaults.  Using the Cloud Services Configuration Client, I am able to create a database connection from the cloud server to the database.  It is an Oracle database connection using the Oracle Provider for OLEDB.

From EA, I use these values when connecting to CLoud:

Name: Whatever name
URL: http://HTTP://servername:804
Model Name:



For the Model Name I cannot for the life of me figure out a name that matches the configuration on the database manager.  The info in the Cloud Services.rft file is vague on the details of this parameter, which I suspect is what is giving me the problem.

The connection string to the db is:
Provider=OraOLEDB.Oracle.1;Persist Security Info=False;User ID=ea_aandc;Data Source=cotsdev

The Database Manager entry is:
oraoledb.oracle.1:ea_aandc@cotsdev

The connection string from EA is:
AANDC --- ;Connect=Cloud=protocol:http,address:servername,port:804;Data Source=ea_aandc;DSN=ea_aandc;

Anyone have insights?

[Geert Bellekens]

I've never used the cloud services, but I always thought you could only do cloud services with the new firebird database.
In fact the cloud service was the very reason they added firebird to the list of supported database types.

Isn't there a whitepaper or explanation somewhere on how to setup cloud services?

Geert

[Andre Lalonde]

I don't think so. It would be pretty restrictive of Sparx to create a cloud service based on only one type of database. If you look at their promo page, http://www.sparxsystems.com/enterprise-architect/cloud-services/cloud-services.html, it clearly states that you can have any RDBMS in the backend.  You can create a new Firebird db as well, fully populated with all the tables though.

[Aaron B]

Hi Andre,

The Cloud Services documentation is still being updated, but should hopefully make the process much more clear once it is finished and officially released.

For an Oracle OleDB connection, the "Model Name" is the name of your data source.  E.g. oraoledb.oracle.1:ea_aandc@cotsdev -> Model Name = "cotsdev".

On the cloud server, also open the properties for the database manager (oraoledb.oracle.1:ea_aandc@cotsdev) and confirm that the "Accept Queries" option is ticked.