By default when a domain is created on a Windows machine a Windows service is created for the Administrator server and the Hawk agent, also when a Windows machine is added to a domain a Windows service is created for the Hawk agent.
This article is to explain how to…
This is a common question and the answer is quiet simple.
The simplest approach to start appnodes and applications automatically after a server boot is to use the ‘startBWAppNode.sh’ scripts generated when an appnode is created.
There is one such script for each appnode and it is located in the…
BusinessWorks 6.X and BusinessWorks Container Edition conveniently allow the creation of Processes exposing or invoking REST APIs using Swagger files previously created, this approach is usually called the design first approach.
But once Processes have been implemented how to manage the case where a new version of the Swagger file…
While exposing or invoking WEB Services it is in some cases needed to access standard or custom HTTP headers. In BusinessWorks 5.X there was no other solution than developing an HTTP Proxy but this is no longer the case in BusinessWorks 6.X and BusinessWorks Container Edition.
To get or set…
While bwagents and appnodes are Java components launched using the standard TIBCO JVM wrapper it is possible under Windows to run them as Windows Services.
Installation of a bwagent as a Windows Service
To set-up the configuration of a Windows service for a bwagent do the following:
- Go to…
In BusinessWorks 6.X the technical runtime configuration parameters and the BusinessWorks parameters are managed in different files:
. The technical runtime parameters are managed in the tra files (this mostly includes JVM parameters and classpath definitions)
. The BusinessWorks parameters are managed in config.ini files (this include appspaces and appnodes…
It is quiet common to have to use different connection configurations in runtime environments, like for example to use a simple HTTP connection configuration in the ‘TEST’ environment and an HTTPS connection configuration with additional parameters, like the keystore file path and password, in the ‘PROD’ environment.
An interesting feature…
This article is the BusinessWorks 5.X version of an article already published for BusinessWorks 6.X and BusinessWorks Container Edition. The original article is available at the following URL :
In most integration scénarios BusinessWorks is processing external events, like WEB Services calls, JMS messages publications or files transfers, that…
In context where numerous REST API or WEB Services are exposed using BusinessWorks 6.X applications it is possible to share the same port between multiple applications to limit the number of ports managed in the network load balancing layer.
This can be done using the following approach:
. Create an HTTP Connector Shared resource in a shared module
. Configure the HTTP Connector Shared resource with the “Share across application” option enabled
. Use the HTTP Connector from the shared module in the applications
. Deploy the applications sharing the same port number in the same AppSpace (it is not possible at operating system level to have two process listening on the same port number)
This approach can also be used to run two versions of the same application on the same port.
While usually BusinessWorks developers are working on a dedicated Windows workstation, it is more and more common with the development of offshore outsourcing to have developers connecting to server farms managed with solutions like Citrix or Microsoft RDS and sharing the same BusinessWorks installation.
This article explain how to configure…