Skip to content

Service

Application servers and middleware

If WebLogic crashes every day at the same time, the cause has a name and can be fixed.

The problem

An undersized application server restarts "on its own", eats all its memory at noon or leaves Forms sessions hanging. The application team spends its days restarting managed servers and nobody has looked at heap, threads, connection pools or GC logs. That is an engineering problem, not bad luck.

How we work

  1. 1

    Capacity diagnosis

    WebLogic and GC log analysis, heap and thread usage, connection pools, Forms Runtime and OHS configuration. We find the actual bottleneck.

  2. 2

    Configuration redesign

    JVM sizing, clusters and managed servers, OHS load balancing, time-outs and session limits consistent with real load.

  3. 3

    Installation and migration

    New WebLogic 12c/14c, Forms & Reports 12c and ORDS environments for APEX and REST, with hardening and SSL certificates.

  4. 4

    Operations

    PSU patching, monitoring, domain backups and documented restart procedures.

Frequently asked questions

We are on Forms 11g. Can we stay there?

You can, but it is out of support and runs on old Java and WebLogic versions with known vulnerabilities. Migrating to Forms 12c is the supported path; modernizing to APEX is the alternative when you want to leave Forms behind.

Can you review a WebLogic installed by our ERP vendor?

Yes. Vendors often install with default values. We review the configuration against real load and propose adjustments without touching the application.

Do you work with Tomcat or only WebLogic?

Mainly WebLogic and the Oracle stack, but we also deploy ORDS on Tomcat and configure Apache or Nginx as a proxy when the design calls for it.