Updated: July 2024
Audience: Everyone
Products Applicable: Jama Connect®
Environment: Self-hosted, Replicated - Traditional/Native, versions 8.x.x and later
Use Case
Restarting Jama Connect® Version 8.0 and Later
As of Jama 8.0, we use Replicated to deploy the "containerized" Jama as one whole application. Replicated deploys different containers, each running a different service, i.e., jamacore, search, elasticsearch, nginx, and tenantmanager, with simple commands. As an administrator of Jama, I know these changes will make your life easier when installing, upgrading, and restarting Jama.
Restarting the Jama Application
Restarting the Jama application is as easy as clicking two buttons -- while Jama is running, navigate to the Replicated Admin Console and select Stop Now in the upper-left-hand widget.
This will stop Jama.
Once Jama has stopped, the widget will update to indicate this. To start Jama back up, select Start Now.
Jama will run through the startup process, which can be tracked in the widget.
Implementation
<full breakdown of steps, screenshots, workflow>
References
- Definitions of key terms
- Hyperlinks to key materials
Please feel free to leave feedback in the comments below.
Comments
0 comments
Please sign in to leave a comment.