This parameter is not used in Windows Authentication mode. If this bridge is executed from a parent application running as a Windows Service, this bridge uses the credentials under which the Windows Service was started. Instead, the login credentials are inferred from the current windows session running this bridge. In Windows Authentication mode, this bridge parameters 'User name' and 'password' are not used. Available only for Oracle and SQL Server databases.
Windows username and password for secure database access. Specify here the authentication mode you want to use:ĭatabase connection user name and password. The master database you want to connect to. E.gįor Oracle, specify the appropriate Oracle connection string you want to connect to. You can also specify a named SQL Server instance. The database server you want to connect to.įor Microsoft SQLServer or Sybase ASE, specify the server DNS address. Refer to your version of erwin for the exact connection types it supports. SQL Server 2000/2005/2008 (using db-lib)Įrwin 7.2.6 and 7.2.7 support the following connection types:Įrwin 7.2.0 supports the following connection types: SQL Server 2005/2008 (using native ODBC)Įrwin 7.3.0 supports the following connection types:Įrwin 7.2.8 supports the following connection types: Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6ĭatabase connection type to connect to the Model Manager.Įrwin 7.3.5, 7.3.10 and 7.3.11 support the following connection types: Provide a trouble shooting package with debug log. Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html Check the 'Allow service to interact with desktop' control, and restart the Windows service. In order to check this, click on the 'Properties' menu of such service, go to the 'Log On' tab, and look in the 'Local System Account' area. Therefore, if this bridge is running within a server launched as a Windows service (rather than a classic Windows desktop application), make sure the check box: 'Allow service to interact with desktop' is set to true. Q: What are the required configuration steps when running this bridge as a Windows service?Ī: This bridge interacts with erwin/ModelManager via its COM based API which may have to display messages on the desktop. If this bridge is running as part of a Windows service, then go to the Windows services and click on the 'Properties' menu of such service, go to the 'Log On' tab, select 'This account' and specify the same user name and password used as Windows session when testing connectivity from erwin to the mart, and restart the Windows service. If this bridge is running as part of a Windows desktop application, then you must log on windows with that user. This bridge must run on behalf of the Windows user that can run the erwin software. Successful import depends upon the erwin API connecting to the database, using a 32-bit database client software.
The version of the database client software installed on the machine running this bridge should match exactly with the version of the database server hosting the Model Manager repository. This erwin installation must be able to connect to and open models in the same Model Manager instance with the same connection information as specified in this bridge parameters. Thus, erwin 7.x must be installed on the machine where this bridge is running. This bridge connects to the Model Manager Repository using the erwin 7.x COM API. PK/FK) as well as the graphical layout of the data models (diagrams).
This bridge also imports all relationships and their implementation (e.g.
This bridge imports data models from erwin Model Manager, including logical only models with Entities, Attributes, Domains, physical only models with Tables, Columns, Data Types, or Logical/Physical models with both. Metadata: Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical LayoutĬomponent: CaErwin7ModelManager version 11.1.0
erwin Data Modeler version 7.x via COM API on Native (.erwin) or Export (.XML) File Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via COM API on Native (.erwin) or Export (.XML) File