.. comment
	
	all inline tags to start with _how_scpt_vm_

	
.. index:: Scripts; How to - Environment variables

.. _how_scpt_vm_top:
.. |br| raw:: html

    <br>

STEPlib SysML: STEPdev virtual machines
######################################################

.. include:: /pages/common/pageunderconstruction.txt
	:start-line: 3

This page explains how to begin with the STEPdev virtual machines.

.. contents:: Contents:
		:local:
		:depth: 1
		:backlinks: top


======================
Build onDemand (beta)
======================

*Ask Vero for location and credentials*

* ensure that your branch is up-to-date with the current branch (the current branch is the one displayed by default on the form),
* fill the form.

You will receive an email when the build is available.

================
Use the full VM
================

The full VM, steplib bookworn, with the environment variables and binaries, is available. Ask AFNeT Services team.

Your only task is to modify the share folders outputdir and wg12-steplib.

.. note:: Remember that the VM has no data and uses the data of your computer by using the share folder.


.. list-table:: *Sharefolders*
   :widths: 10 20 30 40
   :header-rows: 1

   * - Build Type
     - Status
     - Repo
     - git source
   * - current and dev STEPlib-NG
     - mandatory
     - wg12-steplib
     - https://sd.iso.org/bitbucket-pilot/scm/isotc184sc4/wg12-steplib.git
   * - current and dev STEPlib-NG
     - mandatory
     - outputdir
     - any folder, you choose
   * - dev STEPlib-NG
     - mandatory
     - wg12-stepdev, develop branch
     - https://sd.iso.org/bitbucket-pilot/scm/isotc184sc4/wg12-stepdev.git
   * - dev STEPlib-NG
     - mandatory
     - steplib-ng
     - git@github.com:AFNeTServices/STEPlib-NG.git
   * - dev STEPlib-NG
     - optional
     - history
     - git@git2.boost-lab.net:afnet/44xx_history.git
   * - dev STEPlib-NG
     - optional ++
     - boilerplate
     - https://sd.iso.org/bitbucket-pilot/scm/isotc184sc4/boilerplate.git


.. list-table:: *Run script*
   :widths: 20 30 40
   :header-rows: 1

   * - What is built?
     - Mechanism
     - option
   * - entire documentation
     - XMI, DI, schemas et sysml ids are generated only if a change occured in MDZIP.
     - $SLSCRIPTS/STEPDevScripts/build_10303-4442-split.sh –allDoc –cr –b
   * - Force schema generation
     - XMI, DI, schemas et sysml ids are generated only if a change occured in MDZIP.
     - $SLSCRIPTS/STEPDevScripts/build_10303-4442-split.sh –allDoc –cr –b –SCHEMAS
   * - Generate one schema
     - XMI, DI, schemas et sysml ids are generated only if a change occured in MDZIP.
     - $SLSCRIPTS/STEPDevScripts/build_10303-4442-split.sh –allDoc –cr –b -XSD or –allDoc –cr –b -EXP or –allDoc –cr –b -SCH
   * - Force all
     - 
     - $SLSCRIPTS/STEPDevScripts/build_10303-4442-split.sh –all –cr –b
   * - Geneate only the mapping package XMI and DI
     - 
     - sh $SLSCRIPTS/STEPDevScripts/gen4442-diagXMI.sh
   * - Geneate only SysML ids
     - the Test Data package should be removed from Domain_model.xmi
     - java -jar $SAXON9806 -t $SLSCRIPTS/ExtractID/VariablesData242.xml $SLSCRIPTS/ExtractID/CanonicalGenerateIDsXML.xsl


.. warning:: The following content is kept for memory

=====================================================================================================
Build documentation of 10303-239, 10303-243, 10303-4000 and 10303-4442 with the VMs  (need an update)
=====================================================================================================

*The complete documentation is available here* |script IS|


.. list-table:: Build 10303-239 and 10303-243
   :widths: 20 80
   :header-rows: 1

   * - Task
     - Action
   * - **Checkout the repository**
     - See with the team which branch of the Harmonization-fork-STEP-updated-architecture
   * - **Export the diagrams**
     - In MagicDraw, open the mdzip project
       |br| check the image output settings (see Export images from MagicDraw in the |script IS|) 
       |br| select the packages and run the exportDiagrams macro (see Export images from MagicDraw in the |script IS|)
   * - **Check the variables of the STEPDev virtual machine**
       |br| *only for the docker version of the VM*
     - go to docker_container folder, open config.txt file and check:
	   |br| **mount harmo** should be your local Harmonization-STEP-updated-architecture **up-to-date** repository. Please pay attention to the branch.
	   |br| **mount work** should be your current folder. We recommend to use an empty folder.
	   |br| **mount tmp** should be your tmp folder.
	   |br| make sure that 
	   |br| $SLSCRIPTS is /harmo/STEPlib/utils
	   |br| $AP is /harmo/STEPlib/Application_protocols/AP239 or AP243
	   |br| $WORK is /work
	   |br| and ensure that the alias **Build_10303-AP** exists
   * - **Launch the VM**
     - go to the docker_container folder
	   |br| and enter **./launch_vm.sh**
	   |br| when the VM is started, enter **cd $WORK**
   * - **Run the script**
     - Warning: the following folders have to be empty
	   |br| $WORK/output/data
	   |br| $WORK/output/html
	   |br| $WORK/AntPub/output/data/core_model
	   |br| $SLSCRIPTS/AntPub/input/maps
	   |br| $WORK/output/sysml_models_ids.xml
	   |br| $SLSCRIPTS/AntPub/input/sysml_models_ids.xml
	   |br|
       The core_model data should be added in /Antpub/outpub/data This can be done after the generation of the publication.
	   |br| when you are ready, enter **Build_10303-AP 239 plcs** or **Build_10303-AP 243 mossec**
	   |br| You will find the build in your /Antpub/outpub/data/application_protocols. Use home.htm to display the publication.


.. list-table:: Build 10303-4000
   :widths: 20 80
   :header-rows: 1

   * - Task
     - Action
   * - **Checkout the repository**
     - the CTC-harmonization_rebased branch of the Harmonization-fork-STEP-updated-architecture
   * - **Export the diagrams**
     - In MagicDraw, open the Core_model.mdzip project
       |br| check the image output settings (see Export images from MagicDraw in the |script IS|) 
       |br| select the Core_model package and run the exportDiagrams macro (see Export images from MagicDraw in the |script IS|)
   * - **Check the variables of the STEPDev virtual machine**
       |br| *only for the docker version of the VM*
     - go to docker_container folder, open config.txt file and check:
	   |br| **mount harmo** should be your local Harmonization-STEP-updated-architecture **up-to-date** repository
	   |br| **mount work** should be your current folder. We recommend to use an empty folder.
	   |br| make sure that 
	   |br| $SLSCRIPTS is /harmo/STEPlib/utils
	   |br| $CORE is /harmo/STEPlib/Core_model
	   |br| $WORK is /work
	   |br| and ensure that the alias **Build_10303-4000** exists
   * - **Launch the VM**
     - go to the docker_container folder
	   |br| and enter **./launch_vm.sh**
	   |br| when the VM is started, enter **cd $WORK**
   * - **Run the script**
     - Warning: the following folders have to be empty
	   |br| $WORK/output/data
	   |br| $WORK/output/html
	   |br| $WORK/AntPub/output/data/core_model
	   |br| $SLSCRIPTS/AntPub/input/maps
	   |br|
	   |br| when you are ready, enter **Build_10303-4000**
	   |br| You will find the build in your /Antpub/outpub/data/core_model
	   
.. list-table:: Build 10303-4442
   :widths: 20 80
   :header-rows: 1

   * - Task
     - Action
   * - **Checkout the repository**
     - the AP242_ed2_IS_Amendment branch of the Harmonization-fork-STEP-updated-architecture
   * - **Export the diagrams and make the xml**
     - In MagicDraw, open the Domain_model.mdzip project
       |br| check the image output (Tab File/Save as image) settings : png, 150 dpi and 120%
       |br| in the Tools tab, select the Report Wizard, then the Web Publisher 2.0 (in the default template section) and generate the report.
       |br| in the File tab, select the Export to, then the Eclipse UML 2 XMI file.
       |br| in the File tab, select the Save as image, modify the settings to 150%, select all the diagrams and export the images into $WORK/picturesToPrint folder. You can also use the macro "exportDiagramsMacro".
   * - **Check the variables of the STEPDev virtual machine**
       |br| *only for the docker version of the VM*
     - go to docker_container folder, open config.txt file and check:
	   |br| **mount harmo** should be your local Harmonization-STEP-updated-architecture **up-to-date** repository
	   |br| **mount work** should be your current folder. We recommend to use an empty folder.
	   |br| make sure that 
	   |br| $SLSCRIPTS is /harmo/STEPlib/utils
	   |br| $STEPMODTRIAL is your STEPmod repository for the build
	   |br| $WORK is /work
	   |br| and ensure that the alias **Build_10303-4442** exists
   * - **Launch the VM**
     - go to the docker_container folder
	   |br| and enter **./launch_vm.sh**
	   |br| when the VM is started, enter **cd $WORK**
   * - **Run the script**
     - Warning: the following folders have to be empty
	   |br| $WORK/AntPub/input/maps
	   |br| $WORK/output
	   |br| $WORK/AntImp
	   |br|
	   |br| when you are ready, to run the script you have many options. 
	   |br| the full build, with all the pictures, this can take a while: $SLSCRIPTS/STEPDevScripts/build_10303-4442.sh $WORK/magicDraw_files -night -full
	   |br| the full build, with all the pictures, but XSD and EXPRESS generation and AntPub are manually added to the output files: $SLSCRIPTS/STEPDevScripts/build_10303-4442.sh $WORK/magicDraw_files -day -full
	   |br| the same, without the management of the pictures
	   |br| all the doc: $SLSCRIPTS/STEPDevScripts/build_10303-4442.sh $WORK/magicDraw_files -night
	   |br| the doc,  but XSD and EXPRESS generation and AntPub are manually added to the output files: $SLSCRIPTS/STEPDevScripts/build_10303-4442.sh $WORK/magicDraw_files -day
	   |br|
	   |br| the next step is to build, from STEPmod, the 4442 in a change request or an application protocol.
	   

.. sectionauthor:: |veroDub|

.. include:: /keywords.rst