Orion Server

[Twyla Plack]

Monitoranalyze, diagnose, and optimize database performance and DataOps that drive your business-critical applications. Unify on-premises and cloud database visibility, control, and management with streamlined monitoring, data integration, and tuning across multiple vendors.

Modernize your service desk with intelligent and automated ticketing, asset, configuration, and service-level agreement (SLA) management; a knowledge base; and a self-service portal with secure remote assistance. SolarWinds offers an easy-to-use IT service management (ITSM) platform designed to meet your service management needs to maximize productivity while adhering to ITIL best practices.

Ensure user experience with unified performance monitoring, tracing, and metrics across applications, clouds, and SaaS. Robust solutions offering rich visualization, synthetic and real user monitoring (RUM), and extensive log management, alerting, and analytics to expedite troubleshooting and reporting.

Reduce attack surface, manage access, and improve compliance with IT security solutions designed for accelerated time-to-value ranging from security event management, access rights management, identity monitoring, server configuration monitoring and patching, and secure gateway and file transfer.

SolarWinds was founded by IT professionals solving complex problems in the simplest way, and we have carried that spirit forward since 1999. We take pride in relentlessly listening to our customers to develop a deeper understanding of the challenges they face. Our digital agility solutions are built to help companies of any size accelerate business transformation today and into the future.

Monitor, analyze, diagnose, and optimize database performance and data ops that drive your business-critical applications. Unify on-premises and cloud database visibility, control, and management with streamlined monitoring, mapping, data lineage, data integration, and tuning across multiple vendors.

The SolarWinds Orion Platform is a powerful, scalable infrastructure monitoring and management platform designed to simplify IT administration for on-premises, hybrid, and software as a service (SaaS) environments in a single pane of glass.

Orion Application Server is a Java EE application server developed by Swedish company IronFlare AB, founded by Magnus Stenman and Karl Avedal. First released in 1999,[1] Orion claims to be the first commercially available application server with full Java EE support.[2] The current stable version is 2.0.7 which is compliant with Java EE version 1.3.

Oracle Corporation acquired license to the source of Orion in 2001, and developed it as Oracle Application Server Containers for Java EE (OC4J). OC4J and some of its documentation contains reference to the Orion server.[3] Orion developers were involved in maintenance and enhancements of the source for Oracle.[4][5]

IronFlare became an official Java EE licensee[6] in 2003,[1] which enabled them to access the Sun Microsystems compatibility testing tools to ensure correct implementation of the Java EE specification by Orion.

The first is that the app for bigger installs can be be very IO itensive as far the DB server goes. Tons of tiny reads and writes. All in all it will thrash a SQL server pretty hard all by itself, so having it coexist with another app or other DBs means they all will suffer.

Secondly, its a great idea to keed it seperate from your other SolarWinds servers for redundancy. The app is very modular, everything centralizes off of SQL so any part can be rebuilt and so long as your DB is there nothing else needs to be done. The same is for SQL.

not sure, my server is a lot less spec then yours and runs fine, i did have the database on a different server and in the graphs i have lost data, so put the database back on the same server and it's perfect

I would like to add this. For a small install it is perfectly fine. But if you have mutiple modules (especially netflow) and you have a large install you would find its not the best way. You would end up with SQL and SolarWinds fighting for resources and starving each other out.

Ever since we've had the ability to use the My Orion Deployment option. it has never worked. previously it couldn't connect to half my pollers, which were up and running perfectly fine. Support wasn't any help and said to update manually and wait until the next version came out that would resolve it.

We have all ports allowed between our Solarwinds servers. I reopened my original case, they said the reason is most likely all pollers aren't on version 2019.2 or later, but they are all on 2019.4, so I am good there. Hoping to hop on a webex with them to look.

found the issue, within the SWA_InstallationSession table, there was an active UpdateCheck from last month, it was stuck or something. Cleared it out and now I can get past the connecting to scability engines page. Will test on next upgrade how it goes.

RAID recommendations only apply to physical environments. If you have your SolarWinds Platform server installed on a virtual machine, these recommendations do not apply to your environment.

Desktop operating systems, such as Windows 10 or 11, 64-bit Pro or Enterprise, are supported for evaluation environments only. To make a smooth transition from your evaluation to production deployment, SolarWinds recommends that you avoid installing evaluations on desktop operating systems.

If you are not using Windows Authentication, make sure the Anonymous Authentication is enabled for the SolarWinds NetPerfMon website. Anonymous Authentication is used with the default forms-based authentication.

The following recommendations apply to physical environments only. If you have your SolarWinds Platform database installed on a virtual machine, these recommendations do not apply to your environment.

Some common files may need to be installed on the same drive as your server operating system. You may want to move or expand the Windows or SQL temporary directories. For more information, see Working with Temporary Directories.

If you specify any port other than 80, you must include that port in the URL used to access the SolarWinds Platform Web Console. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the web console is :8080.

Communication with the SQL Server Browser Service to determine how to communicate with certain non-standard SQL Server installations. Required only if your SQL Server is configured to use dynamic ports.

This has always been my order of operations for shutdown and startup within any Orion environment and have never had any issues doing it this way. Much of SolarWinds own documentation supports this but doesn't directly go into such detail sadly.

I added some additional clarity and also detailed out the more of the process. I'm pretty meticulous when it comes to the startup because a proper startup procedure can ensure a smooth, clean running Orion environment. I've never seen any documentation that references to the dependencies and in certain cases depending on WHY you're shutting down services you may not want to actually go that far as to stop dependencies. For patching of the servers it's good practice to stop EVERYTHING though. But technically the TFTP server and SFTP/SCP server services are not "Orion" services (at least that's what I was told by SolarWinds Support) - feel free to correct me on that.

That is the same order we use, has always worked fine. Only time we ever have issues is if the SQL server gets pulled out and then it sometimes would not process the queues afterwards and needed a manual process to fix those.

I would like to run a container with a Prefect server on the VM and to access the Prefect UI from anywhere on the network by requesting :4200.

This would allow for a local development of the new Flows and then a simple way to run them. (For anyone who may have used the docker-compose.yaml from Airflow, I would like to reproduce this behavior)

On my PM, I can run Prefect either directly (prefect orion start), or in a container (docker run --network host -it prefecthq/prefect:2-latest prefect orion start). In these cases, I can see the relevant Flows' executions, etc.

The problem arises when I try to relocate my Prefect server onto my VM.

It seems whatever I tries, I ultimately end up with a Can't connect to Orion API at :4200/api. Check that it's accessible from your machine. error message when trying to open the Prefect UI on my PM. Other than this, Prefect seems to be running correctly in the container (i.e I can build, apply and run Flow deployments)

3a8082e126