Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

Installing TeamConnect

To run the installer, start program setup.exe and follow the prompts. For help with the Installer, click the Help button on any Installer screen or see the sections below.

WebDAV and WebLogic

If you use a WebLogic application server, it is important to edit the server's config.xml file to disable basic authentication. If basic authentication remains enabled, it interferes with WebDAV access and Screen Designer. A WebLogic login dialog pops up before the actual TeamConnect login dialog. End users confuse this WebLogic dialog with the TeamConnect one and enter TeamConnect credentials into it, which causes errors.

Disabling basic authentication prevents this first dialog from appearing and the end user sees only the TeamConnect login dialog.

Note for Screen Designer Users: For WebLogic 9.2+, update the config.xml file in weblogic server to allow screen designer to connect by adding the <enforce-valid-basic-auth-credentials> element to config.xml within the <security-configuration> element as shown below. Restart the WebLogic Server and all node managers. (To access the config.xml, navigate to domains/base_domain/config/config.xml)

clipboard_ed2135351794f95c787ee52d59c1b1212.png

Introduction

The TeamConnect Enterprise installer can be run repeatedly. On the very first run of the installer, you must choose "Extract files to install or upgrade TeamConnect Enterprise." On any subsequent runs of the installer, you can choose "Continue using previously extracted files." Normally you would want to use the previously extracted files, because they contain information (such as configuration values) that is customized to your installation. However, you may still choose "Extract files to install or upgrade TeamConnect Enterprise." If you do, you can run the installer as if you were running it for the first time.

Configuration

On this screen, you tell the installer how to modify TeamConnect Enterprise's configuration files. Your choice will vary depending on whether you have an existing version of TeamConnect Enterprise already installed, and whether that version is the current version or an older one.  If there is no existing version of TeamConnect Enterprise, choose "Manually Configure TeamConnect Enterprise" and fill out the configuration information in screens that appear later.  If there is an older version of TeamConnect Enterprise installed, and you want to use the configuration information that is contained in that older version, you have two choices. You can choose "Import Settings (from .war archive)" or "Import Settings (from .xml or .properties files)", depending on which kind of file is available from the older version. The installer will read those files and will extract their configuration information. That information will appear in a series of screens that appear later, and you have the opportunity to accept the existing values or to edit those values.  If there is an older version of TeamConnect Enterprise installed, and you don't want to use the configuration information that is contained in that older version, choose "Manually Configure TeamConnect Enterprise", then fill out the configuration information in screens that appear later.  If there is a current version of TeamConnect Enterprise installed, and you are simply re-running the installer, your choice depends on what you did during the earlier run of the installer.
If you already filled out configuration information in the earlier run, and you don't need to change anything, choose "Skip this step".
 
If you did fill out configuration information in the earlier run, but you now want to change some of the information, choose"Manually Configure TeamConnect Enterprise", then fill out the configuration information in screens that appear later.

If you did not fill out configuration information in the earlier run , choose "Manually Configure TeamConnect Enterprise", then fill out the configuration information in screens that appear later.

Running the Installer

In order to run installer you should have JDK installed on the machine you are running installer and should have JAVA_HOME in classpath. 

clipboard_ed7704348a644e199b49bffe402de89b7.png

clipboard_efa902d424bed571458f968def20bae55.png 

clipboard_e47a851d26f05a9e4531b0305c9d23de8.png 

This step will extract all the artifacts associated with the installer. 

If you have already extracted these artifacts you can point installer to previously extracted location. 

clipboard_e8951e74bb0b275c6f683ad5cce94536d.png

clipboard_e343accc6cbcf0336609ccc77b5ff6e5d.png 

Manually Configure would let you walk through all the properties and add them manually to update the ear/war extracted by installer. 

Import Settings would add the properties file and web.xml to installer and generated the ear/war based on uploaded files. Note: between major upgrades there will be changes in properties file. Addition of new properties or removal of old properties.  

Import Setting from war will take war file as input and will extract required information. 

clipboard_e58886ad45a2e96f14af421fe87ff92c9.png 

TeamConnect supports Weblogic, Tomcat and Websphere. Pick appropriate application server. 

clipboard_ecfc6fbdf8073f07c37e95fbd6c452d04.png 

Log Folder – Physical path for log files in app server location 

jMonitor – location of jMonitor file configuration to be written. Physical location in Appserver 

clipboard_ee52390b8e998a445aef7f5e491ad155a.png 

Eclipselink properties. These properties can be accepted as default. 

clipboard_e8701592e9e11b0dbfbe2c58266188cb5.png 

If Datasource is selected next screen will guide you in adding datasource name. 

If using direct connection to database you will be guided to add database details in the next screen 

clipboard_e50bb159049ff7b1ee71a0a98dcae84a2.png 

clipboard_e43941aee1b3b07efcac7522299bdab06.png 

clipboard_eec12b5da45562734f2fd1e10215f54cf.png 

clipboard_ead1abb5b4baf7968028143971965c669.png 

clipboard_eb02cc0d3b1f7dd733faf8e4460b24f52.png 

ES server location – hostname:portnumber for ES server 

ES Clustername – Unique name for ES CLuster 

clipboard_e3003249e984184dfeb81a2747a738c74.png 

clipboard_e0a9ba9aeb9d1523fe019cce1f20d78e0.png 

clipboard_e12c91f00fc3fc9fc3691c349df215f01.png 

clipboard_e7809d49f23c80b73c8eafdfd60873c96.png 

If you are using a cluster to deploy application you will have to add properties in the next screen. 

clipboard_e1a9d778be49982a9546703cddfd3c98b.png 

Unique Name – This name will be unique for each deployment. If you have Test and Prod pick different names for each installation. 

RMI Port – If you a horizontal cluster adding one port should be sufficient. If you are a vertical cluster where you have two teamconnect application’s running on the same server to avoid port conflict you can specify range so that application will pick available port in range. Ex: 3128-3130 These ports are inclusive meaning 3128, 3129 and 3130 

clipboard_ed12583db45758e7b36ec04cef2e4b486.png 

clipboard_ef3e2773e7906a3f99176ae67edfea07a.png 

 

clipboard_ec4c8f69fcafe47f64b342f56eb815e5d.png 

clipboard_e50e838784613e1f63095bd6f185681de.png 

clipboard_e3c13d41bd57d89d6da73de652d33396f.png 

 

 

 

 

  • Was this article helpful?