deploiementEnvironnement MAPDEPLOY/en

<languages/>
==Introduction==
Since 10.8, it is possible to deploy an environment to another environment (remote or local). This can be very useful for copying the environment setting from Preproduction to a 'production'' environment.

'''Important''': It is important to use it between ''''pre-production and production''' environments (and not development) because this module allows the identical replication of 2 environments (with the possibility of selecting a particular format in order to avoid updating all the formats). If you don't have a staging environment, you should create one or not use this module.

==Principle of operation==
The MAPDPELOY command (accessible via the Exploitation / Environment Deployment meny) allows you to deploy a staging environment to a production environment. 
Indeed, in good practice, it is advisable not to generate the models or to create the rules/actions directly on the production environment but on the pre-production environment. Once the processing(s) have been validated on this pre-production environment, it is necessary to send its configuration to the production environment. (Model, rules, actions, etc.).
To do this, it is very convenient to use the environment deployment menu. This allows you to fill in the recipient hosts, select the format(s) to send or delete or to send the entire configuration (all formats, rules and actions) 

In case you want to send the whole environment (option 11 of the menu), all formats, rules, actions, conversion files, printer settings, etc. will be sent.
In the case of a simple sending of selected formats, only this format and a few configuration files are sent (see table below)


==Menus==
The MAPDEPLOY command has several menus:

<div style="background-color:black">
<span style="background-color:Black;color:Lime;">1. &nbsp;&nbsp;&nbsp;General settings</span></BR>
<span style="background-color:Black;color:Lime;">2. &nbsp;&nbsp;&nbsp;Host server settings</span></BR>
</BR>
<span style="background-color:Black;color:Lime;">11. &nbsp;Deploying a full environment</span></BR>
</BR>
<span style="background-color:Black;color:Lime;">21. &nbsp;Setting up the formats to be deployed</span></BR>
<span style="background-color:Black;color:Lime;">22. &nbsp;Deploying Selected Formats</span></BR>
</BR>
<span style="background-color:Black;color:Lime;">31. &nbsp;Viewing FTP History</span></BR>
</div>

===General settings===
Use this option to fill in the global settings for deployment management. 

*Source MAPPING library
*UCS2 Library
*IFS Path                     
*Intermediate library     
*Prefix of savefiles          
*Savefile library     
*Minimum target version          
*FT log file library 
*Authorized users         
</BR>

'''Context-sensitive help is available via the F1 key.'''

===Host server settings===
This option allows you to populate the destination host servers. The host server will be populated during a deployment (partial or global).
To create a new host, you need to do F6:

*Server Name      
*Description         
*Group code         
*Name or address serv.
*User profile  
*Password        
*Opal Library  
*UCS2 Library   
*IFS Path
</BR>
'''Context-sensitive help is available via the F1 key.'''

===Deploying a full environment===

*Deployment servers
*Source library
*UCS2 Library
*IFS Path
*Batch processing
*Restore savefiles
</BR>
'''Context-sensitive help is available via the F1 key.'''

===Setting up the formats to be deployed===
*Option 1 in front of a format to copy to the host server
*Option 2 in front of a format to delete it on the host server
</BR>
'''Context-sensitive help is available via the F1 key.'''

===Deploying Selected Formats===

*Deployment servers
*Source library
*UCS2 Library
*Intermediate library
*IFS Path 
*Batch processing
*Restore savefiles
</BR>
'''Context-sensitive help is available via the F1 key.'''

===Viewing FTP History===
Displays the log of commands executed on the host server

==Content of transfer savefiles==
===Deploying Selected Formats===
====TRANSFERR1 and TRANSFERS1====

{| class="wikitable"
|-
! Item Name!! type of the object!! Function of the object 
|-
| DEPLOY1 || *LIB || Library containing the formats to be deployed (MAPENV, MAP1, MAP2, etc.)
|-
| DPL003DLY || *PGM || Wait a while for the completion of the ongoing restorations		
|-
| DPL005CPY || *PGM || Program for copying selected formats
|-
| MAP_C016P3 || *PGM || Tests for the existence of a format and copies it
|-
| MAP_C841 || *PGM || Copying afpds files if existing		
|-
| MAP_C841P2 || *PGM || Copying afpds files if existing		
|-
| MAP_MSG || *PGM || Retrieves the text of a message based on its ID		
|-
| MAP_016CHK || *PGM || Tests for the existence of a format in the map and map1 files		
|-
| MAP_016CPY || *PGM || Program for copying a format from library to library		
|-
| MAP_016DEL || *PGM || Partnernair's program to remove a format	
|-
| DPLLIBINT || *DTAARA || Intermediate library name for MAPDEPLOY
|-
| MAPENV || *DTAARA || Dataarea containing the settings of the source environment to be deployed
|-
| CONVERT || *FILE || File containing the conversion rates of the source environment to be deployed
|-
| DPLFORMS || *FILE || A file containing the selected formats to be copied or deleted from the source environment to be deployed
|-
| MAP || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAPARCH2 || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAPARCH3 || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAPLNK || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAPLNKL1 || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAPOBJ || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|- 
| MAP1 || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAP2D || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAP2H || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAP3 || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|-
| MAP3L1 || *FILE || File containing the objects of the formats to be copied from the source environment to be deployed
|}

====TRANSFERR3 and TRANSFERS3====

This savefile contains the contents of the lgobitmap directory and the ttf directory. 
</BR></BR>
<u>Note</u>: This savefile, in a future release, will contain only the contents of the ttf directory, as the lgobitmap directory will have to be managed manually, just as it is already the case for format builds and imports. Indeed, a massive uncontrolled update of the lgobitmap directory can be risky since this directory contains cross-functional resources with several models.

==Ideas for evolution==
*Add a resource check before copying formats
*Manage the M-Connect object part (not currently managed)
*Possibility to do a rollback once deployed on an environment