Top
Systemwalker Operation Manager  Cluster Setup Guide for UNIX
FUJITSU Software
Chapter 5 Cluster Setup Procedure Specific to Systems Using PRIMECLUSTER for Linux > 5.1 Registering Systemwalker Operation Manager with the PRIMECLUSTER System > 5.1.4 Registering cluster applications and resources
PreviousNext

5.1.4 Registering cluster applications and resources

This section describes the procedure for registering Systemwalker Operation Manager as a cluster application.

1) Stop RMS and start the RMS Wizard

Before registering the cluster application, use either ClusterAdmin or the hvdisp command to check that RMS is not running. If RMS is running, stop it on every node in the cluster system using either ClusterAdmin or the hvshut command.

Refer to the PRIMECLUSTER manual for details on the hvdisp and hvshut commands.

Example of how to stop RMS with the hvshut command:

# /opt/SMAW/SMAWRrms/bin/hvshut -a

Start the RMS Wizard by executing the hvw command.

Refer to the PRIMECLUSTER manual for details on the hvw command.

Example of how to start the RMS Wizard using "config" as the configuration file name:

# /opt/SMAW/SMAWRrms/bin/hvw -n config

The "Main Configuration Menu" will be displayed.

Note

If other products are already registered with the cluster system, be sure to specify a configuration file that includes configuration information for all such products. Otherwise, the settings for products that have already been set up may be erased.

2) Set up the userApplication (cluster application).

Use the following procedure to set up the cluster application:

  1. Select "Application-Create".

    linux01: Main configuration menu, current configuration: config
No RMS active in the cluster
 1) HELP                                10) Configuration-Remove              
 2) QUIT                                11) Configuration-Freeze              
 3) Application-Create                  12) Configuration-Thaw                
 4) Application-Edit                    13) Configuration-Edit-Global-Settings
 5) Application-Remove                  14) Configuration-Consistency-Report  
 6) Application-Clone                   15) Configuration-ScriptExecution     
 7) Configuration-Generate              16) RMS-CreateMachine                 
 8) Configuration-Activate              17) RMS-RemoveMachine                 
 9) Configuration-Copy                  
Choose an action: 3

  2. Select "STANDBY".

    Creation: Application type selection menu:
1) HELP                                 7) SCALABLE
2) QUIT                                 8) STANDBY 
3) RETURN                               
4) OPTIONS                              
5) DEMO                                 
6) GENERIC                              
Application Type: 8

  3. Select "ApplicationName" and set up a name for the userApplication.

    Settings of turnkey wizard "STANDBY" (APP1:not yet consistent)
1) HELP                                 4) REMOVE+EXIT         
2) NO-SAVE+EXIT                         5) ApplicationName=APP1
3) SAVE+EXIT                            6) Machines+Basics(-)  
Choose the setting to process: 5

    Select "FREECHOICE".

    1) HELP      
2) RETURN    
3) FREECHOICE
Enter the name of this turnkey type wizard name: 3

    Set "ApplicationName". Specify any name for the application. In the following example, "OP1" is specified as the name of the application.

            >> OP1

  4. Select "Machines+Basics" to perform node settings and basic settings.

    Settings of turnkey wizard "STANDBY" (OP1:not yet consistent)
1) HELP                                 4) REMOVE+EXIT        
2) NO-SAVE+EXIT                         5) ApplicationName=OP1
3) SAVE+EXIT                            6) Machines+Basics(-) 
Choose the setting to process: 6

    Select "AdditionalMachine".

    Machines+Basics (op1:consistent)
 1) HELP                                14) (AutoStartUp=no)         
 2) -                                   15) (AutoSwitchOver=No)      
 3) SAVE+EXIT                           16) (PreserveState=no)       
 4) REMOVE+EXIT                         17) (PersistentFault=0)      
 5) AdditionalMachine                   18) (ShutdownPriority=)      
 6) AdditionalConsole                   19) (OnlinePriority=)        
 7) Machines[0]=linux01RMS              20) (StandbyTransitions=)    
 8) (PreCheckScript=)                   21) (LicenseToKill=no)       
 9) (PreOnlineScript=)                  22) (AutoBreak=yes)          
10) (PostOnlineScript=)                 23) (HaltFlag=no)            
11) (PreOfflineScript=)                 24) (PartialCluster=0)       
12) (OfflineDoneScript=)                25) (ScriptTimeout=)         
13) (FaultScript=)                      
Choose the setting to process: 5

    Select "linux02RMS". Set Machines[0] for the active node and Machines[1] for the standby node.

    1) HELP         
2) RETURN       
3) linux01RMS   
4) linux02RMS   
Choose a machine for this application: 4

    Select "AutoSwitchOver".

    Machines+Basics (op1:consistent)
 1) HELP                                14) (FaultScript=)           
 2) -                                   15) (AutoStartUp=no)         
 3) SAVE+EXIT                           16) (AutoSwitchOver=No)      
 4) REMOVE+EXIT                         17) (PreserveState=no)       
 5) AdditionalMachine                   18) (PersistentFault=0)      
 6) AdditionalConsole                   19) (ShutdownPriority=)      
 7) Machines[0]=linux01RMS              20) (OnlinePriority=)        
 8) Machines[1]=linux02RMS              21) (StandbyTransitions=)    
 9) (PreCheckScript=)                   22) (LicenseToKill=no)       
10) (PreOnlineScript=)                  23) (AutoBreak=yes)          
11) (PostOnlineScript=)                 24) (HaltFlag=no)            
12) (PreOfflineScript=)                 25) (PartialCluster=0)       
13) (OfflineDoneScript=)                26) (ScriptTimeout=)         
Choose the setting to process: 16

    Select "HOSTFAILURE" and "RESOURCEFAILURE".

    In this example, "HOSTFAILURE" and "RESOURCEFAILURE" are selected to trigger a failover when the active node fails or when resources fail. When making actual settings, select values that are appropriate to the actual cluster system operation.

    Set flags for AutoSwitchOver:  Currently set: NO (N)
1) HELP                   4) DEFAULT                7) RESOURCEFAILURE(R)
2) -                      5) NO(N)                  8) SHUTDOWN(S)       
3) SAVE+RETURN            6) HOSTFAILURE(H)         
Choose one of the flags: 6

Set flags for AutoSwitchOver:  Currently set: HOSTFAILURE (H)
1) HELP                   4) DEFAULT                7) RESOURCEFAILURE(R)
2) -                      5) NO(N)                  8) SHUTDOWN(S)       
3) SAVE+RETURN            6) NOT:HOSTFAILURE(H)     
Choose one of the flags: 7

    After making these settings, select "SAVE+RETURN".

    Set flags for AutoSwitchOver:  Currently set: HOSTFAILURE,RESOURCEFAILURE (HR)
1) HELP                   4) DEFAULT                7) NOT:RESOURCEFAILURE(R)
2) -                      5) NO(N)                  8) SHUTDOWN(S)           
3) SAVE+RETURN            6) NOT:HOSTFAILURE(H)     
Choose one of the flags: 3

  5. After performing these settings, select "SAVE+EXIT".

    In this example, "AutoStartUp" is set to "no", so that the cluster application does not start automatically when RMS starts. When performing the actual settings, select values that are appropriate to the actual cluster system operation. Similarly for other values, select values that are appropriate to the actual cluster system operation.

    Machines+Basics (op1:consistent)
 1) HELP                                        
 2) -                                           
 3) SAVE+EXIT                                   
 4) REMOVE+EXIT                                 
 5) AdditionalMachine                           
 6) AdditionalConsole                           
 7) Machines[0]=linux01RMS                      
 8) Machines[1]=linux02RMS                      
 9) (PreCheckScript=)                           
10) (PreOnlineScript=)                          
11) (PostOnlineScript=)                         
12) (PreOfflineScript=)                         
13) (OfflineDoneScript=)                        
14) (FaultScript=)                              
15) (AutoStartUp=no)                            
16) (AutoSwitchOver=HostFailure|ResourceFailure)
17) (PreserveState=no)                          
18) (PersistentFault=0)                         
19) (ShutdownPriority=)                         
20) (OnlinePriority=)                           
21) (StandbyTransitions=)                       
22) (LicenseToKill=no)                          
23) (AutoBreak=yes)                             
24) (HaltFlag=no)                               
25) (PartialCluster=0)                          
26) (ScriptTimeout=)                            
Choose the setting to process: 3

3) Set up resources.

Register resources with the cluster application. The procedure for setting up cluster applications using the following resources is explained below.

Note

  • The mount point used as resource must be defined beforehand in the /etc/fstab directory (for PRIMECLULSTER 4.2A00) or in the /etc/fstab.pcl directory (for PRIMECLUSTER 4.2A30 or later) on all nodes that configure the cluster application. Refer to the PRIMECLUSTER manual for details.

  • Before setting the Gls resource, you need to set the virtual interface and the takeover virtual interface. Refer to the PRIMECLUSTER manual for details.

[Set up Fsystem resources]

  1. Set up Fsystem resources (shared disks) by selecting "LocalFileSystem".

    Settings of turnkey wizard "STANDBY" (OP1:not yet consistent)
 1) HELP                                 9) Procedure:BasicApplication(-)
 2) -                                   10) Symfoware(-)                 
 3) SAVE+EXIT                           11) Procedure:SystemState3(-)    
 4) -                                   12) Procedure:SystemState2(-)    
 5) ApplicationName=OP1                 13) Gls:Global-Link-Services(-)  
 6) Machines+Basics(op1)                14) LocalFileSystems(-)          
 7) CommandLines(-)                     15) Gds:Global-Disk-Services(-)  
 8) Procedure:Application(-)            
Choose the setting to process: 14

    Select "AdditionalMountPoint".

    File systems (Lfs_OP1:not yet consistent)
1) HELP                   4) REMOVE+EXIT            7) (Timeout=180)       
2) -                      5) AdditionalMountPoint   
3) SAVE+EXIT              6) (Filter=)              
Choose the setting to process: 5

  2. Select the mount point to be registered with the cluster application. In the following example, "/disk1" is selected.

    1) HELP      
2) RETURN    
3) FREECHOICE
4) ALL       
5) /disk1    
Choose a mount point: 5

  3. To set the "MONITORONLY" attribute to ON, select "MONITORONLY".

    Set flags for mount point: /disk1 Currently set: LOCAL,AUTORECOVER (LA)
1) HELP                   4) DEFAULT                7) SHARE(S)          
2) -                      5) SYNC(Y)                8) MONITORONLY(M)    
3) SAVE+RETURN            6) NOT:AUTORECOVER(A)     
Choose one of the flags: 8

  4. Select "SAVE+RETURN".

    Set flags for mount point: /disk1 Currently set: LOCAL,AUTORECOVER,MONITORONLY (LAM)
1) HELP                   4) DEFAULT                7) SHARE(S)          
2) -                      5) SYNC(Y)                8) MONITORONLY(M)    
3) SAVE+RETURN            6) NOT:AUTORECOVER(A)     
Choose one of the flags: 3

  5. Select "SAVE+EXIT".

    File systems (Lfs_OP1:consistent)
1) HELP                                 5) AdditionalMountPoint    
2) -                                    6) MountPoints[0]=LAM:/disk1
3) SAVE+EXIT                            7) (Filter=)               
4) REMOVE+EXIT                          8) (Timeout=180)           
Choose the setting to process: 3

[Set up Gls resources]

  1. Select "Gls" to set up Gls resources (takeover IP address).

    Settings of turnkey wizard "STANDBY" (OP1:consistent)
 1) HELP                                 9) Procedure:BasicApplication(-)
 2) -                                   10) Symfoware(-)                 
 3) SAVE+EXIT                           11) Procedure:SystemState3(-)    
 4) -                                   12) Procedure:SystemState2(-)    
 5) ApplicationName=OP1                 13) Gls:Global-Link-Services(-)  
 6) Machines+Basics(op1)                14) LocalFileSystems(Lfs_OP1)    
 7) CommandLines(-)                     15) Gds:Global-Disk-Services(-)  
 8) Procedure:Application(-)            
Choose the setting to process: 13

  2. Select "AdditionalTakeoverIpaddress".

    Gls (Gls_OP1:not yet consistent)
1) HELP                                 4) REMOVE+EXIT                
2) -                                    5) AdditionalTakeoverIpaddress
3) SAVE+EXIT                            6) (Timeout=60)               
Choose the setting to process: 5

  3. The takeover IP address will be displayed. Select the takeover IP address to be registered with the cluster application. In the following example, "000.000.000.00x" is selected.

    1) HELP                                 
2) RETURN                               
3) FREECHOICE                           
4) 000.000.000.00x                      
Choose a takeover IP address for Gls: 4

  4. Select "SAVE+RETURN".

    Set a flag for takeover IP address: 000.000.000.00x
Currently set: 
1) HELP                                 5) AUTORECOVER(A)
2) -                                    
3) SAVE+RETURN                          
4) DEFAULT                              
Choose additonally one of the flags: 3

  5. Select "SAVE+EXIT".

    Gls (Gls_OP1:consistent)
1) HELP                                 5) AdditionalTakeoverIpaddress         
2) -                                    6) TakeoverIpaddress[0]=N,000.000.000.00x
3) SAVE+EXIT                            7) (Timeout=60)                        
4) REMOVE+EXIT                          
Choose the setting to process: 3

[Set up procedure resources]

  1. Select "SystemState3". Select the "SystemState3" resource class specified in "5.1.3 Registering resources that use state transition procedures."

    Settings of turnkey wizard "STANDBY" (OP1:consistent)
 1) HELP                                 9) Procedure:BasicApplication(-)    
 2) -                                   10) Symfoware(-)                     
 3) SAVE+EXIT                           11) Procedure:SystemState3(-)        
 4) -                                   12) Procedure:SystemState2(-)        
 5) ApplicationName=OP1                 13) Gls:Global-Link-Services(Gls_OP1)
 6) Machines+Basics(op1)                14) LocalFileSystems(Lfs_OP1)        
 7) CommandLines(-)                     15) Gds:Global-Disk-Services(-)      
 8) Procedure:Application(-)            
Choose the setting to process: 11

  2. Select "AdditionalProcedureResource".

    SystemState3 Procedure (ProSS3_OP1:not yet consistent)
1) HELP                                 3) REMOVE+EXIT                
2) -                                    4) AdditionalProcedureResource
Choose the setting to process: 4

  3. "OMGR", the state transition procedure specified in "5.1.3 Registering resources that use state transition procedures," will be displayed. Select "OMGR" to be registered with the cluster application. 

    1) HELP       
2) RETURN     
3) OMGR       
4) OMGRMONITOR
Choose an procedure resource name: 3

  4. Select "SAVE+RETURN".

    Set flags for Procedure resource : 
Currently set: TIMEOUT (T1800), PRIORITY (P100)
1) HELP       
2) -          
3) SAVE+RETURN
4) TIMEOUT    
5) PRIORITY   
Choose one of the flags: 3

  5. Select "AdditionalProcedureResourc".

    SystemState3 Procedure (ProSS3_OP1:consistent)
1) HELP                                 
2) -                                    
3) SAVE+EXIT                            
4) REMOVE+EXIT                          
5) AdditionalProcedureResource          
6) ProcedureResources[0]=OMGR:T1800,P100
Choose the setting to process: 5

  6. "OMGRMONITOR", the state transition procedure specified in "5.1.3 Registering resources that use state transition procedures," will be displayed. Select "OMGRMONITOR" to be registered with the cluster application. 

    1) HELP       
2) RETURN     
3) OMGR       
4) OMGRMONITOR
Choose an procedure resource name: 4

  7. Select "SAVE+RETURN".

    Set flags for Procedure resource : 
Currently set: TIMEOUT (T1800), PRIORITY (P150)
1) HELP       
2) -          
3) SAVE+RETURN
4) TIMEOUT    
5) PRIORITY   
Choose one of the flags: 3

  8. Select "SAVE+EXIT".

    SystemState3 Procedure (ProSS3_OP1:consistent)
1) HELP                                        
2) -                                           
3) SAVE+EXIT                                   
4) REMOVE+EXIT                                 
5) AdditionalProcedureResource                 
6) ProcedureResources[0]=OMGR:T1800,P100       
7) ProcedureResources[1]=OMGRMONITOR:T1800,P150
Choose the setting to process: 3

[Set up resources]

After performing these settings, select "SAVE+EXIT" to set up resources with the cluster application.

Settings of turnkey wizard "STANDBY" (OP1:consistent)
 1) HELP                                 9) Procedure:BasicApplication(-)     
 2) -                                   10) Symfoware(-)                      
 3) SAVE+EXIT                           11) Procedure:SystemState3(ProSS3_OP1)
 4) -                                   12) Procedure:SystemState2(-)         
 5) ApplicationName=OP1                 13) Gls:Global-Link-Services(Gls_OP1) 
 6) Machines+Basics(op1)                14) LocalFileSystems(Lfs_OP1)         
 7) CommandLines(-)                     15) Gds:Global-Disk-Services(-)       
 8) Procedure:Application(-)            
Choose the setting to process: 3

4) Perform "Generate" and "Activate" operations.

The procedures for the "Generate" and "Activate" operations are explained below. Perform these operations after verifying that the created cluster application is correct.

  1. Select "Configuration-Generate".

    linux01: Main configuration menu, current configuration: config
No RMS active in the cluster
 1) HELP                                10) Configuration-Remove              
 2) QUIT                                11) Configuration-Freeze              
 3) Application-Create                  12) Configuration-Thaw                
 4) Application-Edit                    13) Configuration-Edit-Global-Settings
 5) Application-Remove                  14) Configuration-Consistency-Report  
 6) Application-Clone                   15) Configuration-ScriptExecution     
 7) Configuration-Generate              16) RMS-CreateMachine                 
 8) Configuration-Activate              17) RMS-RemoveMachine                 
 9) Configuration-Copy                  
Choose an action: 7

  2. Select "Configuration-Activate".

    linux01: Main configuration menu, current configuration: config
No RMS active in the cluster
 1) HELP                                10) Configuration-Remove              
 2) QUIT                                11) Configuration-Freeze              
 3) Application-Create                  12) Configuration-Thaw                
 4) Application-Edit                    13) Configuration-Edit-Global-Settings
 5) Application-Remove                  14) Configuration-Consistency-Report  
 6) Application-Clone                   15) Configuration-ScriptExecution     
 7) Configuration-Generate              16) RMS-CreateMachine                 
 8) Configuration-Activate              17) RMS-RemoveMachine                 
 9) Configuration-Copy                  
Choose an action: 8

  3. Select "QUIT" to end the procedure.

    linux01: Main configuration menu, current configuration: config
No RMS active in the cluster
 1) HELP                                10) Configuration-Remove              
 2) QUIT                                11) Configuration-Freeze              
 3) Application-Create                  12) Configuration-Thaw                
 4) Application-Edit                    13) Configuration-Edit-Global-Settings
 5) Application-Remove                  14) Configuration-Consistency-Report  
 6) Application-Clone                   15) Configuration-ScriptExecution     
 7) Configuration-Generate              16) RMS-CreateMachine                 
 8) Configuration-Activate              17) RMS-RemoveMachine                 
 9) Configuration-Copy                  
Choose an action: 2

For N:1 active/standby configuration, repeat steps 2), 3) and 4) to register N copies of cluster applications (one for each active node) according to the operating environment.

For dual node mutual standby configuration, repeat steps 2), 3) and 4) to register two copies of cluster applications. For "Machines[0]" and "Machines[1]" in "Machines+Basics", ensure that the active and standby nodes are registered in the correct priority order.

5) Cluster service registration of products supported by PRIMECLUSTER

Register with the cluster service using the procedure below.

  1. Register the cluster service for the products supported by PRIMECLUSTER

    Execute the following command on 1 node that configures the cluster system:

    # /etc/opt/FJSVcluster/bin/clrwzconfig

6) Set up exclusive relationship between cluster applications

Perform this procedure for N:1 active/standby configuration only.

Set up exclusive control so that multiple cluster applications do not become active on the same cluster node at the same time. Create a cluster application group in order to set up exclusive relationship.

  1. Start the RMS Wizard to select "Application-Edit".

    linux01: Main configuration menu, current configuration: config
No RMS active in the cluster
 1) HELP                                10) Configuration-Remove              
 2) QUIT                                11) Configuration-Freeze              
 3) Application-Create                  12) Configuration-Thaw                
 4) Application-Edit                    13) Configuration-Edit-Global-Settings
 5) Application-Remove                  14) Configuration-Consistency-Report  
 6) Application-Clone                   15) Configuration-ScriptExecution     
 7) Configuration-Generate              16) RMS-CreateMachine                 
 8) Configuration-Activate              17) RMS-RemoveMachine                 
 9) Configuration-Copy                  
Choose an action: 4

  2. Select an application for which you set up exclusive relationship.

    Edit: Application selection menu (restricted):
1) HELP   
2) QUIT   
3) RETURN 
4) OPTIONS
5) OP1    
Application Name: 5

  3. Select "Machines+Basics".

    Settings of turnkey wizard "STANDBY" (OP1:consistent)
 1) HELP                                 9) Procedure:BasicApplication(-)     
 2) READONLY                            10) Symfoware(-)                      
 3) SAVE+EXIT                           11) Procedure:SystemState3(ProSS3_OP1)
 4) -                                   12) Procedure:SystemState2(-)         
 5) ApplicationName=OP1                 13) Gls:Global-Link-Services(Gls_OP1) 
 6) Machines+Basics(op1)                14) LocalFileSystems(Lfs_OP1)         
 7) CommandLines(-)                     15) Gds:Global-Disk-Services(-)       
 8) Procedure:Application(-)            
Choose the setting to process: 6

  4. Select "LicenseToKill".

    Machines+Basics (op1:consistent)
 1) HELP                                        
 2) -                                           
 3) SAVE+EXIT                                   
 4) REMOVE+EXIT                                 
 5) AdditionalMachine                           
 6) AdditionalConsole                           
 7) Machines[0]=linux01RMS                      
 8) Machines[1]=linux02RMS                      
 9) (PreCheckScript=)                           
10) (PreOnlineScript=)                          
11) (PostOnlineScript=)                         
12) (PreOfflineScript=)                         
13) (OfflineDoneScript=)                        
14) (FaultScript=)                              
15) (AutoStartUp=no)                            
16) (AutoSwitchOver=HostFailure|ResourceFailure)
17) (PreserveState=no)                          
18) (PersistentFault=0)                         
19) (ShutdownPriority=)                         
20) (OnlinePriority=)                           
21) (StandbyTransitions=)                       
22) (LicenseToKill=no)                          
23) (AutoBreak=yes)                             
24) (HaltFlag=no)                               
25) (PartialCluster=0)                          
26) (ScriptTimeout=)                            
Choose the setting to process: 22

  5. Select "FREECHOICE".

    1) HELP      
2) RETURN    
3) FREECHOICE
4) yes       
5) no        
Shut down other applications prior to coming Online: 3

  6. Select "A20X".

    In this example, the group is set as "A", and the cluster application with the highest job priority is set as "20X". When performing actual settings, select values that are appropriate to the actual cluster system operation. Refer to the PRIMECLUSTER manual for details.

            >> A20X

  7. After performing these settings, select "SAVE+EXIT".

    Machines+Basics (op1:consistent)
 1) HELP                                        
 2) -                                           
 3) SAVE+EXIT                                   
 4) REMOVE+EXIT                                 
 5) AdditionalMachine                           
 6) AdditionalConsole                           
 7) Machines[0]=linux01RMS                      
 8) Machines[1]=linux02RMS                      
 9) (PreCheckScript=)                           
10) (PreOnlineScript=)                          
11) (PostOnlineScript=)                         
12) (PreOfflineScript=)                         
13) (OfflineDoneScript=)                        
14) (FaultScript=)                              
15) (AutoStartUp=no)                            
16) (AutoSwitchOver=HostFailure|ResourceFailure)
17) (PreserveState=no)                          
18) (PersistentFault=0)                         
19) (ShutdownPriority=)                         
20) (OnlinePriority=)                           
21) (StandbyTransitions=)                       
22) (LicenseToKill=A20X)                        
23) (AutoBreak=A20X)                            
24) (LicenseToKillWait=yes)                     
25) (HaltFlag=no)                               
26) (PartialCluster=0)                          
27) (ScriptTimeout=)                            
Choose the setting to process: 3

  8. Select "SAVE+EXIT".

    Settings of turnkey wizard "STANDBY" (OP1:consistent)
 1) HELP                                 9) Procedure:BasicApplication(-)     
 2) -                                   10) Symfoware(-)                      
 3) SAVE+EXIT                           11) Procedure:SystemState3(ProSS3_OP1)
 4) -                                   12) Procedure:SystemState2(-)         
 5) ApplicationName=OP1                 13) Gls:Global-Link-Services(Gls_OP1) 
 6) Machines+Basics(op1)                14) LocalFileSystems(Lfs_OP1)         
 7) CommandLines(-)                     15) Gds:Global-Disk-Services(-)       
 8) Procedure:Application(-)            
Choose the setting to process: 3

  9. Repeat steps 2. through 8. for all the applications.

  10. Execute "Generate and Activate operations" in step 4) again.

PreviousNext
Copyright 1995-2022 FUJITSU LIMITED