Delete the concurrent programs
Delete the concurrent programs Prerequisites: If the concurrent program is not in use, the program details need to be entered in the lookup and then this concurrent program needs…
Read MoreTomcat upgradation 8.x to 9.x
Introduction: Apache Tomcat Upgrading from Tomcat 8 to Tomcat 9 is a critical step for taking advantage of the latest features, improved performance, and enhanced security. This blog provides a structured approach for a successful upgrade. Why we need to do: Tomcat 9 introduces support for Servlet 4.0, HTTP/2, and other modern web technologies. Many applications require these features to maintain compatibility and performance. Moreover, Tomcat 8 has reached its end-of-life phase, leaving systems exposed to unpatched vulnerabilities. Challenges and Issues Faced During Upgradation: Configuration Incompatibilities: Configuration files such as server.xml, web.xml, and context.xml may require adjustments to align with Tomcat 9 standards. Application Dependencies: Applications running on Tomcat 8 may rely on deprecated libraries or APIs that are removed in Tomcat 9. Custom Scripts and Integrations: Custom startup scripts, monitoring tools, or integrations might need modifications for compatibility. Steps to Upgrade Tomcat from Version 8 to Version 9: Backup Your Current Setup: l Backup all configuration files: server.xml, web.xml, context.xml. l Backup application WAR files and logs. l Snapshot the current environment to ensure rollback options. Download and Install Tomcat 9: l Download the Tomcat 9 binary from the official Apache Tomcat website. l Extract the archive to a new directory (do not overwrite the existing Tomcat 8 directory). Migrate Configuration Files: l Compare the server.xml, web.xml, and context.xml from Tomcat 8 with the default Tomcat 9 configurations. l Update configurations to align with Tomcat 9 schema. Remove any deprecated elements. Migrate Applications: l Deploy your application WAR files to the webapps directory in the Tomcat 9 installation. l Test applications for compatibility, focusing on deprecated APIs and libraries. Update Custom Scripts: l Modify any startup scripts or custom integrations to reference the new Tomcat 9 directories and binaries. Test the Upgrade: l Start Tomcat 9 using the startup.sh or startup.bat script. l Monitor logs in the logs directory for errors. l Test all deployed applications to ensure they function as expected. Rollback Plan: l If issues are encountered, stop Tomcat 9 and revert to the backup of Tomcat 8.…
Read MoreWeblogic .out files are not rotating issue.
Issue: In WebLogic Server, the .out log files (such as nohup.out or server.out) are not rotating properly, causing them to grow significantly in size—sometimes reaching several GBs. This can lead to disk space exhaustion and make log analysis difficult. Cause of the issue: The primary reasons for .out files not rotating are: WebLogic Logging Configuration – The .out file is typically not managed by WebLogic’s built-in log rotation settings. nohup or Redirected Output – If the server is started using nohup ./startWebLogic.sh &, the output is redirected to nohup.out, which does not rotate automatically. Log Rotation Not Configured – The absence of an external log rotation mechanism (logrotate) can cause .out files to grow indefinitely. Long Running Process – WebLogic keeps writing to the same .out file as long as the process is running. How do we solve: Solution 1: Enable WebLogic’s Built-in Log Rotation If .out logs are managed via WebLogic settings, follow these steps: Login to WebLogic Admin Console Navigate to Servers → Select the target Managed Server. Go to Logging Settings Click on the Logging tab → Click on the General sub-tab. Configure Rotation Settings Rotate Log Files → Enabled Rotation Type → Set to either: By Size (100MB or as needed). By Time (24 Hours). Maximum Number of Retained Files → Set a limit (e.g., 10). Save and Restart WebLogic Server Apply changes and restart the WebLogic server for them to take effect. Solution 2: Redirect Standard Output to a Rotating Log Modify the WebLogic startup script to redirect logs using cronolog: Edit startWebLogic.sh and Modify the nohup Command: ### nohup ./startWebLogic.sh > /path/to/logs/weblogic_$(date +%Y-%m-%d).log 2>&1 &…
Read MoreDeterministic Functions in Oracle
Deterministic Functions in Oracle Overview A deterministic function in Oracle is a function that always returns the same result for the same input values and has no side effects.…
Read MoreRead permission on secondary replica in always-on AG
How to give read permission on secondary replica in always-on AG Purpose of Log shipping: Always On availability groups feature is a high-availability and disaster-recovery solution that provides an…
Read MorePermission on secondary database in loginshipping
How to give read permission on secondary server in log shipping Purpose of Log shipping: SQL Server Log shipping allows databases to automatically send transaction log backups from a…
Read MoreThe Art of Visual Storytelling in UX Design
The Art of Visual Storytelling in UX Design Introduction Visual storytelling has become essential in UX design in today’s fast-paced digital world. It’s about using design elements to convey a…
Read MoreCreating new VM in azure environment
Creating new VM in azure environment Title/ Description of the Process This process outlines the steps to manually or programmatically create a new Virtual Machine (VM) in Microsoft Azure. It…
Read MoreHow to Create a Fine Poster: A Quick Guide
How to Create a Fine Poster: A Quick Guide Introduction Posters are a powerful way to grab attention and communicate messages quickly. Whether you’re promoting an event, brand, or idea,…
Read MoreOverview of Microsoft Azure Cloud Services
Overview of Microsoft Azure Cloud Services Introduction to Cloud Computing: Briefly discuss cloud computing and how Azure fits into the market of cloud service providers. Core Services of Azure: Cover…
Read More