Deploying applications to another environment

Applications can be exported and imported so that they can be shared with other HCL Workload Automation for Z environments. In the new environment, the application can be subsequently updated, replaced, or deleted.

To deploy an application from one environment to another, you can use either the ISPF panels or the Dynamic Workload Console. For details about how to export the job stream definition in the Workload Designer, see the Dynamic Workload Console User's Guide.

To export and import an application:

1. From the main menu, enter fast path 1.4 to display the MAINTAINING APPLICATION DESCRIPTIONS panel, as shown in EQQASUBP- Maintaining application descriptions . Select option 6 (EXPORT - IMPORT) to display the EXPORTING AND IMPORTING panel (EQQDEVOD).
   Note: You can display the EXPORTING AND IMPORTING panel also from the LIST OF APPLICATIONS panel (EQQALSTL) by issuing the X row command.

   ----------------- EXPORTING AND IMPORTING APPLICATIONS --------------------
   Command ===>                                                  
   
   Select one of the following:
   
   1 EXPORT              - Export Application Definitions
   2 IMPORT              - Import Application Definitions
    
   

2. Select option 1 (Export application definitions) to display the EXPORT APPLICATION DEFINITIONS panel (EQQDEVOP), where you specify the name of the application you want to export, and optionally:

   Type

   The type of application, either A for Application, or G for Group definition.

   Subsystem

   The name of the controller subsystem where the application resides.

   A JCL is automatically generated for you to submit EQQYXJPX procedure that exports the application definition into a data set. This data set contains all the Workload Automation Programming Language statements that describe the application and its related objects (such as calendars, workstations, special resources), as shown in Example of a data set containing the Workload Automation Programming Language statements.

   
   
   ****************************  Top of Data ********************************
   ADSTART ADID(MYAPPLTVT5012) STATUS(A) TYPE(A) ADVALFROM(170511) 
    OWNER(DEVOPS)PRIORITY(5)
    CALENDAR(CAL1)GROUPDEF()DSMOOTHING()DLIMFDBK()
   ADOP WSID(CPU1)OPNO(001)JOBN(JOBB) DESCR() DURATION(1)  
    LIMFDBK() HIGHRC() STARTDAY(0) STARTTIME() DLDAY(0) 
    DLTIME()  R1NUM(0) R2NUM(0) PSNUM(1) JOBCLASS() PRTCLASS() FORM() AJSUB(Y)  
    AJR(Y) CLATE(N) TIME(N) AEC(Y) WTO(N) RESTARTABLE() REROUTABLE()  
    CLEANUP(N) CRITICAL(N) POLICY() USRSYS(N) EXPJCL(N) 
    MONITOR(N) CSCRIPT(N) USEXTNAME(N) USEXTSE(N) USESAI(N) 
    WLMCLASS() CONDRJOB(N) NOP(N) MH(N)                                          
   WSSTART WSNAME(CPUA) TYPE(C) REPATTR(A) JOBSETUP(N) TRANSPORT(0)     
    DURATION(0) PRINTOUT(SYSPRINT) DESCR() USAGE(B)
    SPLITABLE(N) R1NAME(R1) R1PLAN(Y) R1CONT(N) R2NAME(R2) R2PLAN(Y)
    R2CONT(N) DEST(TCR1) STC(N) WTO(N) AUTO(N) FTWS(N) WAIT(N)
    VIRTUAL(N) ZCENTRIC(N)REMTYPE()                                             
   WSWD DAY(STANDARD) DESCR()   
   WSIVL START(0000) END(2400) PS(99) R1(99) R2(99) ALTWS()
    

3. In the environment where you want to deploy the application, from the EXPORTING AND IMPORTING panel (EQQDEVOD) select option 2 (Import application definitions) to display the IMPORT APPLICATION DEFINITIONS panel (EQQDEVIP).
   Note: In alternative to the import process, you can automate the deployment of the application by using the Workload Automation plug-in of the IBM UrbanCode Deploy tool. For details about this plug-in, see the IBM UrbanCode Deploy documentation.

   -------------------- IMPORTING APPLICATION DEFINITIONS --------------------
   Command ===>                                                  
   
   Enter data below:
   
   TRANSLATE DATASET ===> STRR.TRANS.TERI.(MEM1)___________________________

   Optionally, you can specify the name of a partitioned data set where to define the translation rules to follow. A sample data set is created for you to edit, as shown in the following example:

                                                   
   ****************************  Top of Data ********************************
   TRANSLATE WS OLD(CPU1) NEW(CPUA)
   TRANSLATE AD OLD(MYAPPLTVT5012) NEW(MYAPPLTVT1722)
   TRANSLATE SR OLD(RESNO) NEW(RESNO22)
   TRANSLATE CL OLD(CAL1) NEW(CAL22)
   TRANSLATE OW OLD(DEVOPS) NEW(DEVOPSA)
   TRANSLATE JS OLD(JOBB) NEW(JOBA)
   TRANSLATE PR OLD(PERIOD1) NEW(PERIODA)
   

   A JCL is automatically generated for you to submit the Workload Automation Programming Language command that deploys the application. The imported application will be finally listed in the LIST OF APPLICATIONS panel, according to the settings specified in the translation data set.