Hitachi

uCosminexus Service Platform Setup and Operation Guide

7.5.3 How to recover when executing HCSC server setup and unsetup

If the HCSC server setup fails, and the HCSC server cannot be set up again, or if HCSC server unsetup cannot be completed even after repeated attempts, take action by performing the following procedure:

Procedure

  1. Execute the following command to delete the repository information:

    cscsvunsetup -user <login user ID> -pass <login password> -csc <HCSC server name> -ignore

    After deleting the repository information, if you need to delete the application, execute steps 2 to 5. If you do not need to delete the application, execute step 5.

  2. Execute the following command to confirm the name of the HCSC application that you want to delete:

    cscapputil -user <login user ID> -pass <login password> -host <IP address>:<port number> -mnguser <management userID> -mngpass <management user password> -j2ee <J2EE server name> -operation list

    Following are the HCSC applications to be deleted. The resources of these applications are not shared in the cluster so delete all applications.

    • CSCMessaging

    • CSCMsgSyncServiceDelivery

    • CSCMsgSyncServiceDeliveryWS

    • CSCMsgAsyncServiceDelivery

    • CSCMsgAsyncServiceDeliveryDBQ

    • cscmsg_async

  3. Execute the following command to stop the HCSC application to be deleted:

    cscapputil -user <login user ID> -pass <login password> -host <IP address>:<port number> -mnguser <management userID> -mngpass <management user password> -j2ee <J2EE server name> -app <application name> -operation stop

  4. Execute the following command to delete the HCSC application:

    cscapputil -user <login user ID> -pass <login password> -host <IP address>:<port number> -mnguser <management userID> -mngpass <management user password> -j2ee <J2EE server name> -app <application name> -operation delete

  5. Delete the resources (database tables, index, or view table) that cannot be deleted, in reference to the table given below.

    However, delete the resources that are shared in the cluster only when you are performing unsetup of the last HCSC server in the cluster.

    There might be cases when each resource is already deleted or a resource is not yet created. Resources need not be deleted if they do not exist.

    Table 7‒64:  Resources used by HCSC server

    No.

    Item

    Resource

    Type

    Shared

    1

    Database table, index, view table

    CSCMSG_S<HCSC server name>_CSC_PERSIST

    T

    N

    2

    CSCMSG_C<class name>_CSC_CONNECT

    T

    Y

    3

    CSCMSG_S<HCSC server name>_LC_DIRECTORY

    T

    N

    4

    CSCMSG_S<HCSC server name>_LC_BPFORMAT

    T

    N

    5

    CSCMSG_S<HCSC server name>_RT_RULE

    T

    N

    6

    CSCMSG_S<HCSC server name>_CV_MAPPING

    T

    N

    7

    CSCMSG_S<HCSC server name>_CV_FORMAT

    T

    N

    8

    CSCMSG_C<class name>_EXECHISTORY

    T

    Y

    9

    CSCMSG_C<class name>_EXECHISTORY_I

    I

    Y

    10

    CSCMSG_C<class name>_CLUSTER#1

    T

    Y

    11

    CSCMSG_C<class name>_HA_ASYNC_ADP#1

    T

    Y

    12

    CSCBP_<class name>_PROCESS

    T

    Y

    13

    CSCBP_<class name>_PROCESS_IDX1

    I

    Y

    14

    CSCBP_<class name>_PROCESS_IDX2

    I

    Y

    15

    CSCBP_<class name>_PROCESS_IDX3

    I

    Y

    16

    CSCBP_<class name>_PROCESS_IDX4

    I

    Y

    17

    CSCBP_<class name>_ACTIVITY

    T

    Y

    18

    CSCBP_<class name>_ACTIVITY_IDX

    I

    Y

    19

    CSCBP_<class name>_LINK

    T

    Y

    20

    CSCBP_<class name>_LINK_IDX

    I

    Y

    21

    CSCBP_<class name>_CORRELATIONSET

    T

    Y

    22

    CSCBP_<class name>_CORREL_IDX1

    I

    Y

    23

    CSCBP_<class name>_CORREL_IDX2

    I

    Y

    24

    CSCBP_<class name>_STR_VARIABLE

    T

    Y

    25

    CSCBP_<class name>_STR_VAR_IDX

    I

    Y

    26

    CSCBP_<class name>_NUM_VARIABLE

    T

    Y

    27

    CSCBP_<class name>_NUM_VAR_IDX

    I

    Y

    28

    CSCBP_<class name>_BOOL_VARIABLE

    T

    Y

    29

    CSCBP_<class name>_BOOL_VAR_IDX

    I

    Y

    30

    CSCBP_<class name>_MSG_VARIABLE

    T

    Y

    31

    CSCBP_<class name>_MSG_VAR_IDX

    I

    Y

    32

    CSCBP_<class name>_MSG_RELATION

    T

    Y

    33

    CSCBP_<class name>_MSG_REL_IDX1

    I

    Y

    34

    CSCBP_<class name>_MSG_REL_IDX2

    I

    Y

    35

    CSCBP_<class name>_MSG_REL_IDX3

    I

    Y

    36

    CSCBP_<class name>_V_ACTIVITY

    V

    Y

    37

    CSCBP_<class name>_V_LINK

    V

    Y

    38

    CSCBP_<class name>_V_STR_VARIABLE

    V

    Y

    39

    CSCBP_<class name>_V_NUM_VARIABLE

    V

    Y

    40

    CSCBP_<class name>_V_BOOL_VARIABLE

    V

    Y

    41

    CSCBP_<class name>_V_MSG_VARIABLE

    V

    Y

    42

    Request reception queue (when cluster type is LB)

    CSC<HCSC server name>ACPT_RCVQ

    Q

    N

    43

    CSC<HCSC server name>ACPT_DBQ

    Q

    N

    44

    Request reception queue (when cluster type is HA)

    CSC<class name>ACPT_RCVQ

    Q

    Y

    45

    CSC<class name>ACPT_DBQ

    Q

    Y

    46

    Temporary file of HCSC server

    ServerProperties_<HCSC server name>

    F

    N

    47

    ServerSetup_<HCSC server name>

    F

    N

    48

    ReceptionProperties_dbq_<HCSC server name>

    F

    N

    49

    ReceptionProperties_ejb_<HCSC server name>

    F

    N

    50

    ReceptionProperties_jms_<HCSC server name>

    F

    N

    51

    ReceptionProperties_soap_<HCSC server name>

    F

    N

    52

    UserReceptionProperties_<HCSC server name>_<Reception ID>

    F

    N

    53

    ServerProperties_<HCSC server name>.old

    F

    N

    54

    ServerSetup_<HCSC server name>.old

    F

    N

    55

    ReceptionProperties_dbq_<HCSC server name>.old

    F

    N

    56

    ReceptionProperties_ejb_<HCSC server name>.old

    F

    N

    57

    ReceptionProperties_jms_<HCSC server name>.old

    F

    N

    58

    ReceptionProperties_soap_<HCSC server name>.old

    F

    N

    59

    UserReceptionProperties_<HCSC server name>_<Reception ID>.old

    F

    N

    60

    ServerPropertiesAct_<HCSC server name>

    F

    N

    61

    ReceptionPropertiesAct_dbq_<HCSC server name>

    F

    N

    62

    ReceptionPropertiesAct_ejb_<HCSC server name>

    F

    N

    63

    ReceptionPropertiesAct_jms_<HCSC server name>

    F

    N

    64

    ReceptionPropertiesAct_soap_<HCSC server name>

    F

    N

    65

    UserReceptionPropertiesAct_<HCSC server name>_< Reception ID>

    F

    N

    66

    ServerPropertiesAct_<HCSC server name>.old

    F

    N

    67

    ReceptionPropertiesAct_dbq_<HCSC server name>.old

    F

    N

    68

    ReceptionPropertiesAct_ejb_<HCSC server name>.old

    F

    N

    69

    ReceptionPropertiesAct_jms_<HCSC server name>.old

    F

    N

    70

    ReceptionPropertiesAct_soap_<HCSC server name>.old

    F

    N

    71

    UserReceptionPropertiesAct_<HCSC server name>_< Reception ID>.old

    F

    N

    72

    _cscmsg_cnfrqdbq_<HCSC server name>.xml

    F

    N

    73

    _cscmsg_cnfrqejb_<HCSC server name>.xml

    F

    N

    74

    _cscmsg_cnfrqjms_<HCSC server name>.xml

    F

    N

    75

    _cscmsg_cnfrqsoap_<HCSC server name>.xml

    F

    N

    76

    _cscmsg_cnfrqsorp_<HCSC server name>.xml

    F

    N

    77

    _cscmsg_cnfrq_<HCSC server name>_< Reception ID>.xml

    F

    N

    78

    inf

    F2

    N
Legend:

I: Indicates an index. #2

T: Indicates a database table #2

V: Indicates a view table #2

Q: Indicates Reliable Messaging.#3

F: Indicates an HCSC server temporary file.#4

F2: Indicates that it is the output destination directory for saving the system management information of the HCSC server #5

Y: Indicates that the resource is shared in the cluster.

N: Indicates that the resource is not shared in the cluster.

Note#1

Execute the following SQL statement to acquire the list of information set in the corresponding table:

SELECT * FROM CSCMSG_C<class name>_CLUSTER;

  • When the acquired list does not contain information other than that of the HCSC server whose setup failed

    Run the following SQL and delete the corresponding table:

    DROP TABLE CSCMSG_C<class name>_CLUSTER;
DROP TABLE CSCMSG_C<class name>_HA_ASYNC_ADP;

  • When the acquired list contains information other than that of the HCSC server whose setup failed

    Run the following SQL and delete the corresponding record:

    DELETE FROM CSCMSG_C<class name>_CLUSTER
WHERE CSC_SERVER_NAME='<HCSC server name that has failed in setup and unsetup>';
COMMIT;
Note#2

Delete the database table, index, and view table by executing the SQL command (DROP).

Note#3

To delete the Reliable Messaging queue, execute the hrmstop command to migrate to the management status, and then execute the hrmdelque command. For details about the command, see "8.3.8 hrmdelque (deleting queue) " in "Reliable Messaging".

Note#4

For the HCSC server temporary file, delete the files in "<Installation directory of Service Platform>\CSC\system\msg".

Note#5

Delete the resources in the directory specified in the hcscserver-data-filepath property of the HCSC server setup definition file. When a directory is not specified in the hcscserver-data-filepath property, delete the resources in the default directory of hcscserver-data-filepath property.

Important note

  • For deleting an HCSC server on the J2EE server, use the cscapputil command. You cannot delete with the J2EE server commands.

  • Use the cscapputil command only when recovering from a failure. Do not use the command during normal operations and setup.

  • The Service Platform system might collapse if you delete an application with the cscapputil command. Therefore, perform operations carefully.

To Page Top

Trademarks

All Rights Reserved. Copyright (C) 2022, Hitachi, Ltd.