Starting the webMethods Integration Server
The webMethods Integration Server must be running in order for clients to execute services. If you are using the server in a development environment, it must be running in order for your developers to build, update, and test services using the Software AG Designer.
Keep the following points in mind when starting Integration Server:
Integration Server stores some configuration files and log files on disk. Make sure that there is enough free disk space on the
Integration Server machine to accommodate these files. Running out of disk space can affect performance and can lead to errors.
Make sure that the external database to which
Integration Server connects is available before staring
Integration Server. If the database is unavailable at
Integration Server startup, some components, such as the scheduler, will not be initialized and will not work properly.
Note:
During installation of Integration Server, an option can be set requiring that the password for the Administrator user account be changed immediately upon successful log in to Integration Server Administrator. If so, the Administrator user account password must be changed before the server can do anything else. Any requests sent to Integration Server before the Administrator password is changed will be rejected.
For information about starting Microservices Runtime, see Developing Microservices with webMethods Microservices Runtime .