This creates the servers folders under the domain. Run \startWeblogic.cmd for the first time. If the is created with the production mode option: Use plain communication for the node managers by updating the communication type for the node managers as shown in the following example: This file is found in the \nodemanager directory.Įdit the \config\config.xml file. In the nodemanager.properties file, set SecureListener=false. You can find the start up script inside the newly created domain, that is, the \bin directory. To complete the configuration of the cluster: This file can be used to override all the field values for either mapping strategy:įieldMapperThenValueMapping: The RecordValue attribute values as shown in the following example can be changed:įigure 6-23 Configuration Wizard Configuration Summary Page
The RTLog Generator application relies heavily on the XML-based mapping which provides extensibility and a way to maintain/upgrade features for the application. The following example is an excerpt from this file:įigure 6-3 RTLogMappingBean.xml File Excerpt This is a spring configuration XML file that provides metadata for the FieldMapper and Record Accessor beans which get injected into the RTLog Generator business logic classes. Rtlog-generator-log4j.xml: This file configures the logging levels for the RTLog Generator application. You do not make any changes to this file. This file specifies the format of the RTLog record as specified by ReSA. ResaFileDropDir = C:/RTLOG_Weblogic/Output/ReSA ProcessingDir = C:/RTLOG_Weblogic/Output/Store/RTLOGS For more information, see "WebLogic Cluster Setup".įollowing is an example of the three properties: This directory needs to be created manually.ĬlusterNodeNumber: This property should only be enabled when running in a clustered environment. It should be configured to the location where ReSA is looking to receive the RTLog files. ResaFileDropDir: This directory path specifies the destination for the RTLog files this system is producing. This directory needs to be created manually. ProcessingDir: This directory path specifies the location that RTLog Generator will use to build its RTLog files as it receives data from Xstore Office.
This file contains three properties (key value pairs): Once the configuration file is extracted to the configured directory, verify the following files: If nothing is specified, the RTLog Generator application will fail on startup with error messages in the server logs. If either of the two does not exist, the context parameter is used. The JVM argument takes the precedence over the default location, that is, C:\.
See Figure 6-1.įigure 6-2 Example of context-param Field Update If the WebLogic domain is created with a Node manager, the same argument can be passed from the Administration Console in the Arguments field. Pass a JVM argument to the server startup script and bounce the server: These default locations can be overridden/changed by using one of the following ways: These directories are the default locations where the RTLog Generator application will look for the configuration files.
To set up the external configuration features:Įxtract the configuration file's content into the C:\ directory if installing on Microsoft Windows or /usr/local/ on Linux OS. To integrate with ReSA on premise, rtlog-gen-config-resa-onprem.zip should be used to externally configure and extend the RTLog Generator's functionality. To integrate with ReSA on cloud, rtlog-gen-config-resa-cs.zip should be used to externally configure and extend the RTLog Generator's functionality.
Starting from Xstore release 18.0, the RTLog Generator application is shipped with two configuration zip files: Bounce the WebLogic server after making any configuration level changes.