Installation Check List - Team for Capella 1.4.2 Chosen Team for Capella deployment mode: [ ] local clients + server [ ] remote clients + server on the same VM (Virtual Machine) [ ] remote client VM + server VM System requirements [ ] Check the recommended system requirements in the Installation Guide (3.2 section) [ ] Check the antivirus exceptions described in the Installation Guide (3.2 section) [ ] Check that the server and/or VMs have access to the Internet (at least during installation, as it could be required to download/install additional tools like Java, NotePad++, .Net framework, ..) [ ] For the deployment mode with VMs, the Remote Desktop Protocol will be needed, check that it is installed and that ports between 50000 and 60000 are opened (random port) Chosen License server deployment mode: [ ] License server on the same host than the Team for Capella server [ ] License server on a distinct VM/server [ ] License token (.ols files) generation asked to Obeo [ ] License token (.ols files) received from Obeo [ ] Check License server system requirements (JRE matching at least JavaSE-1.8, 128Mo RAM allocated to the JVM process and a minimum of 20Mo of disk space while operating) Team for Capella Server - ip/hostname: - repository port: - repository names: - scheduler manual launch port: - scheduler service port: - scheduler service name: - console port: License server - ip/hostname: - license server port: - license monitoring port - number of tokens: System Requirements (see Installation Guide) - Expected number of concurrent users: - Server VM - Required amount of RAM: - Required number of cores: - Client VM - Required amount of RAM - Required number of cores: Network checks [ ] Team for Capella server is visible from client (ping TeamForCapellaServerIP from a client computer or VM regarding the chosen deployment mode) [ ] Team for Capella server repositories port is open (2036 by default, for example with Nmap: nmap -p 2036 TeamForCapellaServerIP) [ ] Team for Capella server telnet port is open (12036 by default, see jobs parameters in Jenkins to change it) [ ] License server visible from the Client/Client VM (ping licenseServerIP) [ ] License server chosen port is open (for example with Nmap: nmap -p portNumber licenseServerIP) [ ] Network latency checks JVM checks [ ] Check the default JVM (java -version) [ ] If several JVMs are installed, reference the right one using the -vm arg in the server.ini and eclipse.ini files. Installation checks [ ] Existing installation update ? See data migration process described in Installation Guide, decide if you stop the previous version or if you change the ports, service names, .. [ ] Follow the Server installation procedure described in the Installation Guide (3.4.1 section) [ ] Follow the license server installation procedure described in the Installation Guide (3.4.3 section) [ ] Follow the Client installation procedure described in the Installation Guide (4.2 section) [ ] Verify the installation (server and client procedure described in the Installation Guide: 3.4.4 and 4.2.3 sections) Server Configuration (optional checks / additional security measures) [ ] Team for Capella installation access folder restriction needs ? [ ] Authentification/User rights managements in Team for Capella: do not forget to add an user for the Importer job nor to configure the job [ ] Need for additional repositories ? [ ] Need to use SSL mode ? (TCP by default) [ ] Need to activate the durable locks mode ? [ ] Need to define several repository ? [ ] See additional configuration options in Installation Guide and Team for Capella integrated help (Help > Help Contents > Team for Capella Guide) Scheduler / Jenkins [ ] Install Jenkins as a Windows Service (might require to install .Net framwork 3.5 if not already present) [ ] Check the default jobs configuration described in the Installation Guide (3.5 section) [ ] Check and configure the jobs periodicity (stop server, start server, backups, .. ) [ ] Configure and activate the "Start license server" job if you want to manage it from the Scheduler [ ] Check the Import jobs behavior: the -closeServerOnFailure can be changed if the server must stay alive even if an import has failed for example. [ ] Scheduler/Jenkins user rights needs ? (decide and configure who can see/launch/delete/complete jobs or job results, see Team for Capella integrated help or Jenkins official documentation) [ ] Complete jobs if additional repositories have been added [ ] Check if the number of available executors is sufficient regarding the defined jobs and their periodicity [ ] See additional configuration options in Installation Guide and Team for Capella integrated help (Help > Help Contents > Team for Capella Guide) Client Configuration [ ] Add the license key in the client eclipse.ini before zipping it and shipping it to the end users. [ ] Update default preferences if required (for example: repository location, port and name, see sampleInstallationReport.txt) [ ] Update default workspace location and name in eclipse/configuration/config.ini (for example: osgi.instance.area.default=@user.home/TeamForCapella/workspace to change the default value, osgi.instance.area to force the value (equivalent to -data in eclipse.ini)) [ ] If the chosen deployment mode is one with remote clients (shared installation), update the configuration area in eclipse/configuration/config.ini (for example osgi.configuration.area.default=@user.home/TeamForCapella/configuration or use the equivalent -configuration in eclipse.ini)) [ ] If the chosen deployment mode is one with remote clients (shared installation), check that several users can concurrently launch the client and play with the tool. [ ] See additional configuration options in Installation Guide and Team for Capella integrated help (Help > Help Contents > Team for Capella Guide) Miscellaneous [ ] Check the need to create a sandbox [ ] Define its granularity: it could be a sandbox repo, a sandbox server or a full sandbox with client, scheduler, server. [ ] Regarding the chosen granularity, do not forget to check or change the cdo server port, repo name, db path, Jenkins port, windows service name (sandbox might not require to be installed as a service).