The EntireX RPC Server for .NET allows standard RPC clients to communicate with .NET server assemblies. It works together with the .NET Wrapper. This document covers the following topics:
Software AG Command Central is a tool that enables you to manage your Software AG products remotely from one location. Command Central offers a browser-based user interface, but you can also automate tasks by using commands to remotely execute actions from a terminal or custom script (for example CI servers such as Jenkins, or generic configuration management tools such as Puppet or Chef).
Command Central can assist with the following configuration, management, and monitoring tasks:
Infrastructure engineers can see at a glance which products and fixes are installed, where they are installed, and compare installations to find discrepancies.
System administrators can configure environments by using a single web user interface or command-line tool. Maintenance involves minimum effort and risk.
Release managers can prepare and deploy changes to multiple servers using command-line scripting for simpler, safer lifecycle management.
Operators can monitor server status and health, as well as start and stop servers from a single location. They can also configure alerts to be sent to them in case of unplanned outages.
The Command Central graphical user interface is described under Administering the RPC Server for .NET using the Command Central GUI. For the command-line interface, see Administering the RPC Server for .NET using the Command Central Command Line.
The core Command Central documentation is provided separately and is also available under Guides for Tools Shared by Software AG Products on the Software AG documentation website.
The RPC Server for .NET uses the .NET Wrapper Runtime to call the .NET Server assemblies. .NET Server assembly skeletons are generated with the .NET Wrapper.
For more information on the RPC Server for .NET, .NET Wrapper Runtime and .NET Framework Configuration, see Customizing the RPC Server.
RPC requests are worked off inside the RPC server in worker threads, which are controlled by a main thread. Every RPC request occupies during its processing a worker thread. If you are using RPC conversations, each RPC conversation requires its own thread during the lifetime of the conversation. The RPC server provides two worker models:
FIXED
The fixed model creates a fixed number of worker threads. The number of worker threads does not increase or decrease during the lifetime
of an RPC server instance.
DYNAMIC
The dynamic model creates worker threads depending on the incoming load of RPC requests.
For configuration with the Command Central GUI, see Worker Scalability under Configuration > Server.
For technical details, see parameter endworkers under Administering the RPC Server for .NET with Local Scripts.