Configure middleware descriptors
Middleware descriptors provide information about different middleware platform types that includes middleware discovery intervals, enablement, and installation information.
To add or change installation information to the middleware descriptor, we must know the installation paths of the middleware software to configure.
We can edit the following middleware descriptors that are provided with the product:
- Application server
- Liberty profile server
- Apache HTTP server
- JBoss server
- PHP server
- Apache Tomcat server
- BEA WebLogic server
- Custom HTTP server
- WebSphere Application Server Community Edition server
Tasks
- Edit middleware platform descriptor properties using one of the following two options:
- Use the middleware descriptor administrative tasks command to edit the properties.
- In the administrative console, click...
System administration > Middleware descriptors > middleware_platform_name.
If we are using an Apache HTTP server, WAS Community Edition, or PHP run time: Configure the interval at which the discovery function of the middleware platform runs. Supply a Discovery interval and units for this discovery interval in seconds, minutes, hours, or days. To disable middleware discovery, enter -1 in the Discovery interval field. Click OK to save these changes. This automated discovery is supported for Apache, WAS Community Edition, and PHP run times only.
- Edit the middleware platform version details using a wsadmin command, or using the administrative console. The version properties vary depending on the middleware platform type, for example, for some types, we can edit the session affinity descriptor.
- Use the middleware descriptor administrative tasks command to edit the version detail.
- In the administrative console, click the version to edit.
For Apache web servers, WAS Community Edition servers, and PHP servers, if we installed the phpRuntime, wasceRuntime, or apacheWebServerRuntime to a location other than the default path, we can edit the installation location. We can also define multiple installation locations. Do not include installation locations for server installations for which discovery is not preferred, such as centralized installation manager installations of WAS Community Edition. If we change or remove an installation location from servers that were previously discovered, changes to those servers are no longer discovered.
When enabled, automated discovery can run for Apache, WAS Community Edition, and PHP run times that we configured.
Related:
Middleware nodes and servers Add middleware servers to configurations Configure passive HTTP session affinity in the on demand router Manage middleware servers Intelligent Management: middleware descriptor administrative tasks