2.4.3 Operating the test environment set up with HCSC easy setup functionality

This section describes method to operate the test environment set up by using HCSC easy setup functionality and information required for operating the test environment.

Organization of this subsection
(1) Starting and stopping the test environment
(2) Information required for operating the test environment
(3) Operating the embedded database
(4) Troubleshooting

(1) Starting and stopping the test environment

Following table describes the method to start and stop the test environment.

Table 2-5 Method to start and stop the test environment

Start and stop targetMethod to start and stop
Embedded database#To start:
From [Start] menu of Windows, select [Cosminexus]-[Start database].

To stop:
From [Start] menu of Windows, select [Cosminexus]-[Stop database].
Services of embedded database#When you start or stop the machine of test environment, the test environment is automatically started or stopped.
  • Management Server
  • Administration Agent
When you start the machine of test environment, the test environment is automatically started and when you stop the machine of test environment, the test environment is automatically stopped.
  • Performance Tracer
  • J2EE server
  • HCSC server
  • Standard reception
To start:
From [Start] menu of Windows, select [Cosminexus]-[Start test server].

To stop:
From [Start] menu of Windows, execute [Cosminexus]-[Stop test server].
Note#
Implement only when you have selected [Model with DB/without RM] or [Model with DB/RM] in HCSC easy setup screen.

(2) Information required for operating the test environment

When you set up the test environment by using HCSC easy setup functionality, the required information is automatically set up. To perform testing and debugging by using the test environment, you must know the information set when setting up the test environment with HCSC easy setup functionality.

Information set in test environment set up by using the HCSC easy setup functionality is described as follows.

Hint
You can customize the information set in the test environment set up by using the HCSC easy setup functionality, after setting up the test environment. For details on how to customize, see "2.4.4 Customizing a Test Environment".
(a) Information of user ID and password

Following table shows the information of user ID and password set in the test environment set up with HCSC easy setup functionality:

Table 2-6 User ID and password set in the test environment

Setting destinationUser ID and password that is setInitial valueDescription
Embedded database#1User IDadmin#2Authentication identifier of table owner (USRID of environment variable)
Passwordadmin#2Password of table owner (PSWD of environment variable)
Management ServerManagement user IDadminManagement user ID for logging in to Management Server(use with cmx_build_system -change command#3)
PasswordadminPassword or logging in to Management Server(use with cmx_build_system -change command#3)
HCSC-ManagerHCSC-Manager login user IDadminUser ID for logging in to HCSC-Manager(use with cscsvstart command #4)
HCSC-Manager login passwordadminPassword for logging in to HCSC-Manager(use in cscsvstart command#4)
HCSC serverUser ID of the database used by HCSC serveradminUser ID of database used by HCSC server(use with csccompodeploy command#4)
Password of database used by HCSC serveradminPassword of database used by HCSC sever(use with csccompodeploy command#4)
Note#1
Set when you select [Model with DB/without RM] or [Model with DB/RM] in HCSC easy setup screen.
Note#2
Handled with upper case characters "ADMIN" in the embedded database.
Note#3
For this command, see "cmx_build_system (building Web system)" in "Application Server Reference Guide".
Note#4
For cscsvstart command, see "cscsvstart(starting HCSC server)" in "Service Platform Reference Guide". For csccompodeploy command, see "csccompodeploy(deploying HCSC component)" in "Service Platform Reference Guide".

(b) Information of the port number

Following port number is set in the test environment set up with HCSC easy setup functionality. For port number, you can specify any value in HCSC easy setup screen. For details on value specified in HCSC easy setup screen, see "Table2-4 Items to be input in HCSC easy setup screen".

Embedded database(only when [Model with DB/without RM] or [Model with DB/RM] is selected in HCSC easy setup screen)
  • DB connection port number
Management Server
  • HCSC server operation port number
  • Logical server operation port numberr
  • End request receipt port number
  • Internal communication port number
  • In-process Naming Service port number
Administration Agent
  • Agent connection port number
J2EE server
  • Web service MDB(WS-R)receipt port number
  • SessionBean receipt port number
  • MDB(DB queue)receipt port number
  • Operation check port number
  • Simple Web server port number
(c) Information of name

Following table describes information such as host name or server name set in the test environment set up with HCSC easy setup functionality. When you change the server name with [Server name] tab on HCSC easy setup screen, name after change is set.

Table 2-7 Name set in the test environment

Setting destinationName that is setInitial valueDescription
Embedded database#1Host nameLocalhostHost name of embedded database(DB_HOST of environment variable)
Management ServerHost nameLocalhostHost name of Management Server(use with cmx_build_system -change command#2)
HCSC-ManagerManager nameManagerHCSC-Manager unique identification name for HCSC-Manager to identify Manager(use with cscsvstart command#3)
PRFServer namePRFServer name of PRF
J2EE serverServer nameJ2EEServerName of connection destination J2EE server(use with cjstartsv command#2)
Host nameLocalhostHost name of connection destination J2EE server
System name unique in entire system to which Reliable Messaging is linkedRMSystem name unique in entire system to be linked with Reliable Messaging(HRM_SYSTEM_NAME of environment variable)
Resource adapter nameReliable MessagingDisplay name of target RAR file(use with cjdeployrar command#2)
DB_Connector_for_HiRDB_Type4
DB_Connector_for_HiRDB_Type4_Cosminexus_RM
ClusterCluster nameClusterCluster name
HCSC serverHCSC serverHCSCHCSC server name(use with cscsvstart command#3)
Note#1
Set only when you select [Model with DB/without RM] or [Model with DB/RM] in HCSC easy setup screen.
Note#2
For cmx_build_system -change command, see "cmx_build_system (setting up Web system)" in "Application Server Command Reference Guide". For cjstartsv command, see "cjstartsv (starting J2EE server)" in "Application Server Command Reference Guide". For cjdeployrar command, see "cjdeployrar (deploying resource adapter)" in "Application Server Command Reference Guide".
Note#3
For this command, see "cscsvstart (starting HCSC server)" in "Service Platform Reference Guide".

(d) Other information

When you select [Model with DB/without RM] or [Model with DB/RM] in HCSC easy setup screen, following information is set in the embedded database of the test environment set up with HCSC easy setup functionality.

Data (RD area) storage destination
For information of RD area storing destination, you can specify any value in HCSC easy setup screen. For details on the value specified in HCSC easy setup screen, see "Table2-4 Items to be input in HCSC easy setup screen".
Area size of the database e to be created
Area size (DB_SIZE of environment variable) of the database to be created is set.
Initial value is "660MB".

(3) Operating the embedded database

For the embedded database set up by using HCSC easy setup functionality, you must regularly check the unused area of database. If unused area is less, release blank pages or blank segments, or delete the unnecessary execution history. For details, see " 2.5 Operating an embedded database set up with the HCSC Easy Setup functionality".

(4) Troubleshooting

If you continue to set up or unset up HCSC server, deploying or deleting HCSC components and sending the requests by using HCSC easy setup functionality, there is a risk of insufficiency of unused segments in the embedded database.

If you face the insufficiency of the unused segments, implement the following countermeasures:

Method 1: Release the empty segments within embedded database
  1. Search the table within the embedded database with SQL Executer.
    For details on how to search the table, see pdsql command in "HiRDB SQL Executer Online Help".
  2. Issue pdreclaim command for all the tables starting with "CSC" and "RM" from the result of searching with step 1., and re-use blank pages by releasing.
    For details on pdreclaim command, see the "HiRDB Command Reference Guide".
Method 2: Re-edit tables within the embedded database
  1. Search tables within the embedded database with SQL Executer.
    For details on how to search tables, see pdsql command in "HiRDB SQL Executer Online Help".
  2. Issue pdrorg command for all the tables starting with "CSC" and "RM" from the search results of step 1, and reorganize tables.
    For the details on how to reorganize tables, see the contents related to reorganization of table in "HiRDB System Operation Guide".
    For details on pdrorg command, see the "HiRDB Command Reference Guide".
Method 3: Resetting up the test environment built with HCSC easy setup functionality
Unset up the test environment built with HCSC easy setup functionality once and then reset up. Embedded database is recreated with this work.
However, when you reset up the test environment, created service adapter or business processes are also deleted. Therefore, export repository in advance, then reset up the test environment and import the repository after reset up.