Difference between revisions of "GDL/9.0/Deployment/Verify GDL Docker Container"
(Published) |
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2") |
||
(2 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
|Standalone=No | |Standalone=No | ||
|DisplayName=Verify GDL Docker Container | |DisplayName=Verify GDL Docker Container | ||
− | |Platform= | + | |Platform=GenesysEngage-cloud |
|Context=Verification steps for GDL Docker. | |Context=Verification steps for GDL Docker. | ||
|Section={{Section | |Section={{Section | ||
|sectionHeading=Verify Docker Deployment | |sectionHeading=Verify Docker Deployment | ||
− | | | + | |Standalone=No |
− | | | + | |ComingSoon=No |
+ | |Status=No | ||
+ | |alignment=Vertical | ||
+ | |structuredtext=The successfully running GDL Docker containers can be verified by using the following command in another instance of Command Prompt (login as vagrant ssh in root folder) | ||
<code>'''docker ps'''</code> | <code>'''docker ps'''</code> | ||
Line 14: | Line 17: | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Verify using Management API | |sectionHeading=Verify using Management API | ||
− | | | + | |Standalone=No |
− | | | + | |ComingSoon=No |
+ | |Status=No | ||
+ | |alignment=Vertical | ||
+ | |structuredtext=The successfully running GDL Docker containers can also be verified by accessing Management station API. | ||
# Click [http://192.168.33.10:8080/api/swagger-ui.html#/ here] to access the Management Station API with default username as '''admin''' and password as '''admin'''. (The IP address of the Swagger API UI can be modified in Vagrant properties file in<span>config.vm.network "private network" property)</span> | # Click [http://192.168.33.10:8080/api/swagger-ui.html#/ here] to access the Management Station API with default username as '''admin''' and password as '''admin'''. (The IP address of the Swagger API UI can be modified in Vagrant properties file in<span>config.vm.network "private network" property)</span> | ||
# <span>Click '''Cluster API''' (Operations pertaining to metadata in Kafka Cluster) to verify the number of brokers and access points of Kafka. It returns the port numbers of Kafka access points where the messages are coupled to Kafka layers (GDL).</span> | # <span>Click '''Cluster API''' (Operations pertaining to metadata in Kafka Cluster) to verify the number of brokers and access points of Kafka. It returns the port numbers of Kafka access points where the messages are coupled to Kafka layers (GDL).</span> | ||
Line 23: | Line 29: | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Execute Deployment Test | |sectionHeading=Execute Deployment Test | ||
− | | | + | |Standalone=No |
− | | | + | |ComingSoon=No |
+ | |Status=No | ||
+ | |alignment=Vertical | ||
+ | |structuredtext=Click '''Command API''' (Execute deployment test) to execute the deployment test cases of Kafka layers. It is an essential test case where the pseudo messages are published and consumed within the Kafka ports. | ||
# Click '''Try it out'''. | # Click '''Try it out'''. | ||
# Select '''start'''. | # Select '''start'''. |
Latest revision as of 02:32, July 25, 2020
Verification steps for GDL Docker.
Verify Docker Deployment
The successfully running GDL Docker containers can be verified by using the following command in another instance of Command Prompt (login as vagrant ssh in root folder)
docker ps
It lists the successfully running Docker containers such as Zookeeper, Kakfa, and tenant-api Docker containers.
Verify using Management API
The successfully running GDL Docker containers can also be verified by accessing Management station API.
- Click here to access the Management Station API with default username as admin and password as admin. (The IP address of the Swagger API UI can be modified in Vagrant properties file inconfig.vm.network "private network" property)
- Click Cluster API (Operations pertaining to metadata in Kafka Cluster) to verify the number of brokers and access points of Kafka. It returns the port numbers of Kafka access points where the messages are coupled to Kafka layers (GDL).
- Click Try it out.
- Click Execute.
- The Response Body JSON file returns the number of available brokers and its port numbers.
Execute Deployment Test
Click Command API (Execute deployment test) to execute the deployment test cases of Kafka layers. It is an essential test case where the pseudo messages are published and consumed within the Kafka ports.
- Click Try it out.
- Select start.
- Click Execute. (Ensure all your Kafka layers are up before executing the test case)
- The Response Body JSON file returns the message as command started.
The test cases take approximately seven to ten minutes to verify the deployment of Kafka layers. After ten minutes, follow the given steps to access test results.
- Click Try it out.
- Select result.
- Click Execute.
The Response Body JSON file returns the result of executed test cases.The success message indicates the flawless data transfer between producer and consumer.