08. Install X-ERP

Now infrastructure becomes an application. The key difference between “files copied” and “X-ERP installed” is a reproducible, secured operating framework.

Why this station counts

X-ERP runs as an ASP.NET Core application behind IIS. Version, application path, pool, service identity, environment values ​​and log path must match and remain traceable in updates.

The resilient process

1. Check package version, checksum and release notes.
2. Create versioned application path, website and your own application pool.
3. Unpack or install X-ERP into the intended path.
4. Set minimum file and execute permissions for the pool identity.
5. Start the website locally and check logs before external releases follow.

Functional test - only then continue

• Application package and version are documented.
• Application Pool remains started stably.
• Configuration and log paths are writable and program files are protected.
• Local call reaches the application without repeated errors.

If the result is not correct

• Manual changes in the program directory are lost during the update.
• A shared pool couples independent applications.
• Write permissions that are too broad make program files changeable.

This is what you take with you

The X-ERP application runs as a clearly defined, maintainable IIS unit.

Video

▶Install X-ERP

Further information / source

Related topics

1. For system administrators – set up servers and create company databases › 05. Install .NET Hosting Bundle
2. For system administrators – setting up servers and creating company databases › 09. X-ERP-Configurator
3. For system administrators – set up servers and create company databases › 10. Set up certificate

Frequently asked questions