LAKSHMI WEBLOGIC/SOA ADMIN

Catch & CatchAll block Catch block 1. This is used to handle specific fault 2. Store fault information in fault variable 3. We can add more than one Catch block in one BPEL process. CatchAll block 1. This is used to handle any type of fault. 2. We need to use functions to get the fault details. 3. We can add only on CatchAll block in one BPEL process. Function we use to get Fault Name and Fault description in CatchAll block We use ora:getFaultName() to get fault name  ora:getFaultAsString() function to get fault description  Fault Handling framework Oracle SOA Suite provides generic fault management framework to handle the faults. We use this framework to handle the fault that occur during invocation time. Catch blocks and Fault Handling Framework CatchAll Blocks 1. We use Catch & CatchAll block to handle all types of error. 2. These can be used only for BPEL component. 3. We can use this for all BPEL templates (Sync, Async, Oneway). Fault Han...

JDBC: Problem Overview: Stale database connections in WebLogic occur when connections remain open but are no longer in use by applications. This leads to: High CPU usage  (database server struggles with managing dead connections) High memory consumption  (each idle connection consumes resources) Database breakdown  (connection pool exhaustion leading to "ORA-00020: maximum number of processes exceeded" or similar errors) Root Causes: Improper Connection Handling Missing  connection.close()  in application code (JDBC leaks) T ransactions left open without commit/rollback JDBC Pool Misconfiguration Missing  TestConnectionsOnReserve  or  InactiveConnectionTimeout Overly large  MaxCapacity  with no proper cleanup Network/DB Failures Database restarts or network drops leaving connections in a zombie state Long-Running Queries Queries that hang indefinitely (e.g., due to locks or bad SQL) Detection Methods: WebLogic Console Checks Navigat...

The solution for Log files not rotating   Check the Status of the Server ./startWeblogic.sh ./startManagedWeblogic.sh <manageservername> Another option: Check in the console. Check the disk Space(if fit is full, Delete the logs and then  restart the Server) du –kh (folder) df –kh (filesystem) If the avail capacity is  45% 90% If full , mv <source > <destination> Delete, rm –rf <filename: adminserver.log> Major Server Errors: Check the Status of Servers. ./startWeblogic.sh ./startManagedWeblogic.sh <manageservername> Need to do from console. Check the Server logs /apps/bea/domain/gwmp_destop/logs Adminserver.log Managedserver.log For this Database Errors, Check the Connection pool and Datasource. Services->jdbc->connectionpool,datasource Check out the Deployment Descriptors. Weblogic.xml,web.xml Based on the logs we can change Configuration Changes, Make the Changes and then restart instances one by one if...

Server Lifecycle Management: # Start Admin Server $DOMAIN_HOME/startWebLogic.sh  # Unix %DOMAIN_HOME%\startWebLogic.cmd  # Windows # Start Managed Server $DOMAIN_HOME/bin/startManagedWebLogic.sh <server_name> <admin_url> # Graceful stop $DOMAIN_HOME/bin/stopWebLogic.sh  # Admin $DOMAIN_HOME/bin/stopManagedWebLogic.sh <server_name> t3://admin_host:port Force Kill (if hung): kill -9 $(pgrep -f "weblogic.Name=<server_name>")  # Unix taskkill /F /PID <pid>  # Windows Deployment Commands: WLST (WebLogic Scripting Tool): # Deploy app deploy('my_app', '/path/to/app.ear', targets='AdminServer') # List deployments ls('/AppDeployments') # Undeploy undeploy('my_app', targets='AdminServer') Command-Line (weblogic.Deployer): java weblogic.Deployer -adminurl t3://localhost:7001 -deploy /path/app.war Log Inspection: Tail Logs in Real-Time tail -f $DOMAIN_HOME/servers/AdminServer/logs/AdminServer.log Search for Er...

To configure the Two Way SSL. On the Admin Server Select  SSL tab: Advanced options Two Way Client Cert Behaviour should be  Client Cert Requested and Enforced. Save it. Now if you will can try to access the Admin Console over SSL then you will throw some SSL Handshake exception.  Because of this process  two way SSL, Client is also requested to submit the certificate and we have not configured any certificate for our client  So, we need to configure the certificate for the Client and for that  again we need the Certificates for the Client. We will be using the same CertGen utility of Weblogic Server to create the certificate. java utils.CertGen <-certfile >ClientCert <-keyfile>ClientKey <-keyfilepass> keypass Again it will create four certificates for the client. To convert the client certificate into the PKCS12 format because the browsers generally accept PKSC12 keystore format for storing certificates. Go to t...

ANT script solution for deploying multiple SOA composites (SAR files) to Oracle SOA Suite in a single execution. 1. Prerequisites: Oracle SOA Suite 11g/12c installed ANT (1.9+) with Oracle SOA ANT tasks configured Admin server credentials Composite SAR files ready for deployment 2. ANT Script Template Save as deploy-composites.xml <project name="SOA-Composite-Deployer" default="deploy-all" basedir="."> <!-- Properties Configuration --> <property file="build.properties"/> <!-- SOA ANT Task Definitions --> <taskdef name="scac" classname="oracle.tip.tools.ant.SCACompose" classpath="${oracle.home}/soa/modules/oracle.soa.common_11.1.1/tasks.jar"/>  <taskdef name="sca-deploy" classname="oracle.tip.tools.ant.SCADeploy"  classpath="${oracle.home}/soa/modules/oracle.soa.common_11.1.1/tasks.jar"/> <!-- Main Deployment Target --> <target name="depl...

Alarms are  automated notifications  triggered when a system detects an abnormal condition that requires  human attention  to resolve. Unlike automated recovery processes, alarms highlight scenarios where: Manual intervention  is necessary (e.g., decision-making, troubleshooting). Automated fixes  are not possible (e.g., missing dependencies, corrupted data). Timely action  is critical to prevent cascading failures. Key Characteristics of Such Alarm Event-Driven Triggered by specific conditions (e.g., a file not arriving on time, a job failing repeatedly). Example: A scheduled ETL job fails because an expected input file is missing. Requires Human Judgment The system cannot auto-resolve (e.g., deciding whether to proceed with incomplete data or wait). Example: A payment processing system flags a transaction for fraud review. Escalation Mechanisms If unacknowledged, alarms escalate (e.g., email → SMS → phone call → on-call engineer). Example: A server ...

Autosys provides a set of commands that run essential utility programs for defining,controlling and reporting on jobs. Commonly Used Utilities in AutoSys Here are the main utilities in AutoSys: autouxlo Purpose :  Display event logs for a specific job Usage:  autouxlog -j <job_name> autotrace Purpose:   Traces a job's execution path. Usage: autotrace -j <job_name> autorep Purpose :  Reports job information (status, definitions, run history). Usage: autorep -j <job_name>        # Job status autorep -j <job_name> -q     # Job definition autorep -s                    # Job status for all jobs autosyslog: Purpose:  Shows the AutoSys scheduler log (used for troubleshooting) Usage:  autosyslog -e OR -s -e  for Event Processor log -s  for Scheduler log job_depends: Purpose:  Graphically shows job dependencies. Usage: job_depends -J <job_name...

Components: Autosys system components are:- • Event Server • Event Processor • Remote Agent Event Server (or Autosys Database) Data Repository that stores Autosys system information,events and job definitions. The Autosys Db is termed ‘Data Server’ which describes a server instance Event Processor Interprets and processes all the events it reads from the Autosys Database A program that actually runs Autosys Scans the database for processing events. Checks if the events satisfy the starting conditions of the job and the determines the actions Remote Agent Temporary process started by the event processor to perform a specific task on a remote machine It starts the command specified for a given job, sends running and completion information about a task to the Event Server If it is unable to transfer the information, it waits and tries until it successfully communicates with the DB I nteraction Between System Components: Step1: From the Autosys event...

Autosys architecture has two types of machines:- Server Machine: The machine on which the Event Processor and Event Server reside Client Machine: The machine on which the Remote Agent resides and where Autosys jobs are run. What is an Autosys Instance? A version of Autosys software running as an Autosys server,with one or more clients,on single machine or on multiple machine An instance uses its own Event Server and Event Processor by operating independently of all other Autosys instance. Multiple instances can run and schedule jobs on the same machine without affecting other instances on that machine. Example: Payroll Processing System: Scenario: A company uses Autosys to automate its payroll workflow across  Development (DEV)  and   Production (PROD)  environments.  The jobs run on multiple servers (Linux/Windows). Autosys Machines Definition : Logical representations of  servers  where jobs execute (e.g.,  linux_payroll1 ,  ...

Workflow: Step1:   The Event Processor scans the Event Server for the next event to processor.If no event is ready,the Event Processor scans again in 5 seconds. Step2: The Event Processor reads from the Event Server that an event is ready.The autosys-job definition and attributes are retrieved from the Event Server,including the command and the pointer to the profile file to be used for the schedule. Step3: The Event Processor processes the event.The Event Processor attempts to establish a connection with the Remote Agent on the client machine and passes the autosys-job attributes to the client machine.The Event Processor sends a CHANGE_STATUS event marking in the Event Server that the autosys-jobs in STARTING state. Step4: The Remote Agent is invoked using the UserID and Password passed from the Event Processor. Step5: The Remote Agent receives the autosys-job parameters and sends an acknowledgement to the Event Processor Step6: The Remote ...