Home
Implementation Guides
Implementation Guide for Red Hat JBoss Enterprise Application Platform
FAQs and troubleshooting
This section covers the frequently asked questions and troubleshooting issues.
Troubleshooting Issues
This topic contains the list of Troubleshooting issues related to Cloud Native Unica release.
Question 1
Stopping and Restarting an Application Server

Implementation Guides
- Implementation Guide for Apache Tomcat
- Implementation Guide for Red Hat JBoss Enterprise Application Platform
  - Docker, Kubernetes, and Helm
    In this release, we have implemented Cloud Native Unica using Docker, Kubernetes, and Helm.
  - ELK Overview
    The ELK Stack is a collection of three open-source products: Elasticsearch, Logstash, and Kibana.
  - Pre-installation configurations
    Before installing or upgrading to Cloud Native Unica, you should complete some configurations.
  - Cloud Native Unica Helm release architecture
    The following is a diagrammatic representation of the Cloud Native Unica Helm release architecture:
  - Helm chart configuration
    Before you start the installation or upgrade of Cloud Native Unica, you should configure the appropriate configMap YAML files.
  - Installation and verifying the installation
  - Post installation configurations
    The following topics contain details about post installation configurations related to the products of Unica.
  - Migration of on-premises applications to Cloud Native Unica
  - Cloud Native Unica upgrade
    To upgrade an earlier version of Cloud Native Unica to a newer version, complete the following steps:
  - Scaling Unica containers
    Scaling a deployment ensures creation and scheduling of new Pods. Scaling increases the number of Pods to the new required state. Kubernetes also supports autoscaling of Pods.
  - Deployment monitoring
    The Kubernetes Dashboard is a web-based user interface to monitor deployments.
  - Using Red Hat OpenShift
    You can use OpenShift to develop and runcontainerized applications. OpenShift allows applications, and the data centers that support them, to expand from just a few machines and applications to thousands of machines that serve millions of clients.
  - Product utilities
    You can execute all the utilities of the Unica products in their assigned pods.
  - Using secret to avoid passwords in plain text
    To use a secret to avoid using passwords in plain text, complete the following steps:
  - Using AWS Secrets and Configuration Provider with Kubernetes Secret Store CSI Driver
    AWS Secrets Manager securely retrieves secrets from the AWS Secrets Manager for Amazon Elastic Kubernetes Service (Amazon EKS) Kubernetes pods.
  - FAQs and troubleshooting
    This section covers the frequently asked questions and troubleshooting issues.
    - Frequently Asked Questions
      This topic contains the list of FAQs related to Cloud Native Unica release.
    - Troubleshooting Issues
      This topic contains the list of Troubleshooting issues related to Cloud Native Unica release.
      - Question 1
        Stopping and Restarting an Application Server
      - Question 2
        Cannot select supported locales for Plan.
      - Question 3
        ActiveMQ URL does not work.
  - Uninstalling the chart
  - Appendix: Description of Helm chart parameters
    The following topics contain description of the parameters present in the configMap YAML files:
- Implementation Guide for Oracle WebLogic Server

Question 1

Stopping and Restarting an Application Server

About this task

Sometimes, you might have to stop and restart the application server. For example, if you have modified some settings and these modified settings require restarting the application server.

Procedure

Before stopping and restarting JBoss, complete the following steps.

Save your work and confirm that all users have logged off.
Locate the running docker container using the command kubectl get pods.
Access the container using the command kubectl exec -it <name of the container> bash.
Locate the running process using the command ps -ef.
Kill the process using the command kill -9. This stops the JBoss server.
Note: Always start the server in the background. If you do not start the server in the background, you cannot access the command prompt till the server starts. If the server takes too long to start, press CTRL+C to terminate the JBoss server.
To restart the server, access the bin directory of JBoss and start the server by running the command standalone.sh in the background.
To exit the docker container, press CTRL+D.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.