Borland Together (via UML 2.x XMI) - Export
Bridge Specifications
| Vendor | Borland |
| Tool Name | Together |
| Tool Version | 6.x to 2006 |
| Tool Web Site | http://www.borland.com/us/products/together/ |
| Supported Methodology | [Object Modeling] Data Store (Object Model UML Class Diagrams) via UML XMI File |
SPECIFICATIONS
Tool: Borland / Together version 6.x to 2006 via UML XMI File
See http://www.borland.com/us/products/together/
Metadata: [Object Modeling] Data Store (Object Model UML Class Diagrams)
Component: OmgUml2XmiExport.BorlandTogether version 11.2.0
OVERVIEW
This export bridge generates an XMI (XML Metadata Interchange format) file with objects, attributes, inheritance, types, relationships and graphical layout (diagrams). The actual standard specifications provided by the OMG (Object Management Group) are often extended for proprietary reasons by the target tool vendor, and in many cases the metadata written to the XMI file is then not consumed by the target tool. A high-level description of the metadata coverage is provide in the LIMITATIONS.
REQUIREMENTS
n/a
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html
SUPPORT
Provide a troubleshooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope |
| File | Generates an XML file compliant to the Object Management Group (OMG) Unified Modeling Language (UML) XML Metadata Interchange (XMI) file format. | FILE | *.xml | Mandatory | |
| UML Version | Allows you to specify UML version your tool supports. | ENUMERATED | 2.1 | 2.1 | |
| Miscellaneous | INTRODUCTION Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g. -connection.cast MyDatabase1="MICROSOFT SQL SERVER" Some options can be used multiple times if applicable, e.g. -connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2; As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g. ETL/Miscellaneous.txt JAVA ENVIRONMENT OPTIONS -java.memory <Java Memory's maximum size> (previously -m) 1G by default on 64bits JRE or as set in conf/conf.properties, e.g. -java.memory 8G -java.memory 8000M -java.parameters <Java Runtime Environment command line options> (previously -j) This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g. -java.parameters -Dname=value -Xms1G The following option must be set when a proxy is used to access internet (this is critical to access https://repo.maven.apache.org/maven2/ and exceptionally a few other tool sites) in order to download the necessary third-party software libraries. Note: The majority of proxies are concerned with encrypting (HTTPS) the outside (of the company) traffic and trust the inside traffic that can access proxy over HTTP. In this case, an HTTPS request reaches the proxy over HTTP where the proxy HTTPS-encrypts it. -java.parameters -java.parameters -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass |
STRING |
Bridge Mapping
Mapping information is not available