Messages

1

General Board / Re: "String literal too long" importing

« on: September 13, 2007, 05:51:43 am »

Dear all,

we are using EA with the latest patch but still the message "String literal too long" appears if we try to import a package from our .eap file to Oracle repository.

We often use text longer than 4000 chars in "Tag values" property...

Any advices?
Thank you in advance,
Petr

2

General Board / Security and access control to different projects

« on: August 13, 2007, 06:07:51 am »

Dears,
we are using EA 6.5 (corporate licence) with underlying Oracle database repository. EA is used by approx. 50 users working on different projects which are stored in the same database. We would like to restrict access of the users only to the projects (=packages) they are working at. It would not be a problem if all the users had read-only access to all models, however, the modification/delete should be restricted only to the team members of the project.

I have several related questions:

1) is it possible to control "modify" access to particular packages with "Require user lock to edit" enabled? I mean is it possible to allow the lock functionality on particular project/package only to a members of some security group? Let's say there would be a "project_X", user group "users_X" and only the users of this group were allowed to lock this package "project_X" for editing? I could not find the way how to do it with the feature enabled. Do you have some hints?

2) So, the only way I have found is to lock the projects (packages) with the "Group lock, locking group may still edit" and specify the proper user group with all the team members who should be allowed to modify the project. The setting is applied recursively even for the subpackages. Unfortunately, if somebody creates a new package under such locked one, the setting is not applied to it recursively and everybody can modify/delete the new package (or new element or whatever..). The only solution I have found is to apply the lock again, which is not very user-friedly. Is there some EA setting, where I can specify that the lock should be applied in automated way even for the packages/elements newly created?

Or is there some better way how to restrict access of the users to particular repository content?

Thank you very much for help, I hope the description is clear although a bit longer ...

regards,
Petr

3

General Board / Re: "Error creating XML parser" when run

« on: July 08, 2007, 09:53:09 pm »

Thank you all for your help.
I have already solved the problem - Microsoft XML (MSXML) libraries were missing and that was the problem..



Regards,
Petr

4

General Board / "Error creating XML parser" when running

« on: June 13, 2007, 05:26:02 am »

Good afternoon,

I have a problem with running EA. After installing EA and trying to launch it, the message ""Error creating XML parser" is displayed and it is not possible to launch it.

Do you know what could be the problem and how to fix it?

Thank you in advance,
Petr

5

General Board / Error transferring .EAP to Oracle repository ...

« on: May 16, 2007, 11:04:48 pm »

Hi,

I have problem when transferring our .EAP file to newly created Oracle repository. When using "Project transfer", I get several oracle errors "ORA-01031 Insufficient privileges" after creating table "usystables". The same happens even if I try to transfer EAExample.eap or other simple examples..

After the transfer, it is possible to open the model elements from the repository, however I cannot create a new one - I got error "ORA-02289 sequence does not exist".

Do you have any idea what is the problem? Is it that the user which is transferring the project to repository has no privileges for creating new Oracle sequences? (so maybe "GRANT CREATE SEQUENCE TO ... could help...??).

I would like to know what has to be set up in Oracle before asking our DBA specialist to do it (as I have no DBA privileges..).

Thank you very much,
P.