Specifying Custom Engine Properties in Designer

-
Specifying custom engine properties in TIBCO Designer can either be done by modifying the designer.tra, or by creating a properties.cfg file. The advantage of the latter is that you don't have to restart TIBCO Designer every time you need to change the value of the property. Also the properties.cfg overrides the value of the engine properties you have specified in designer.tra. You can comment out the property by prepending a hashtag (#) to the property.

Before loading and running the process in Designer tester, you need to specify the full file path to your properties.cfg file.



Here are some of the common engine properties:

#Enabling web service authentication via LDAP
java.property.com.tibco.bw.security.login.jaas=true
java.property.java.security.auth.login.config=jaas.conf
java.property.TIBCO_SECURITY_VENDOR=true
java.property.com.entrust.toolkit.security.crypto.random.DRBGusingSHA512=true

#Salesforce Connection Forward Proxy Configuration
java.property.com.tibco.plugin.salesforce.proxyHost=http-proxy.com
java.property.com.tibco.plugin.salesforce.proxyPort=8080

#Salesforce Connection SSL Configuration
java.property.com.tibco.security.EntrustLast=true
java.property.com.entrust.toolkit.x509.CertVerifier.ForceV1CertAsCA=true
java.property.TIBCO_SECURITY_VENDOR=j2se
java.property.javax.net.ssl.trustStore=%TIB_JAVA_HOME%/lib/security/cacerts
java.property.javax.net.debug=ssl

#SOAPRequestReply Debug Configuration
java.property.com.tibco.plugin.soap.trace.inbound=true
java.property.com.tibco.plugin.soap.trace.outbound=true
java.property.com.tibco.plugin.soap.trace.filename=C:\SOAP\soap.txt
java.property.com.tibco.plugin.soap.trace.pretty=true

#These are used to disable the input or output validation of SOAPRequestReply
java.property.com.tibco.plugin.soap.SOAPSendReceiveActivity.NoOutputValidation=true
java.property.com.tibco.plugin.soap.SOAPSendReceiveActivity.NoInputValidation=true

#HTTP Persistent Connection
bw.plugin.http.client.usePersistentConnectionManager=true
bw.plugin.http.client.connectionTimeout=3600000
bw.plugin.http.client.maxConnectionsPerHost=5
bw.plugin.http.client.maxTotalConnections=100
bw.plugin.http.client.checkForStaleConnections=true

#REST/JSON Plug-in Configuration
java.property.com.tibco.plugin.restjson.xml2json.checkEmptyElement=false
java.property.com.tibco.plugin.restjson.xml2json.empty2null=false
java.property.com.tibco.plugin.restjson.proxyHost=http-proxy.com
java.property.com.tibco.plugin.restjson.proxyPort=8080
java.property.com.tibco.plugin.restjson.proxyUser
java.property.com.tibco.plugin.restjson.proxyPwd

#HTTP Proxy Connection
java.property.http.proxyHost=http-proxy.com
java.property.http.proxyPort=8080

#This is to disable SNI
java.property.jsse.enableSNIExtension=false

Comments

Post a Comment

Popular posts from this blog

XML Schema and JSON Schema Validation in Mule 4

-
Image
Exposing an API to be consumed by client applications entails a lot of challenges. Apart from a good API definition and documentation, you also need to ensure that the request payload submitted to your API endpoints are valid and conforms to the expected data structure. Although it is not required, I think some of the advantages to validate a request payload are: Establish a service contract which is a form of agreement between the service provider and the service consumer. This means that, in order to successfully consume an API, a client application needs to strictly follow a specification "for the request payload" called a data schema . Establish data integrity which ensures that all incoming data submitted to the API are "in a format that is expected". It doesn't make sense to process malformed data. For instance, if you are inserting data to a relational database, it would be more beneficial to first check mandatory (or required) fields before processing th
Read more

Parsing a JSON String and Converting it to XML in TIBCO

-
Image
If you have the REST & JSON Plug-in for TIBCO BusinessWorks, parsing and rendering a JSON string into XML is a straightforward task. We are often using XML in TIBCO, because XML is the most common format that is used to transform data using XSLT and XPath language. There are two ways we can parse and render JSON text: using an XML Schema, and using Java classes. Of course, XML Schema is already very handy, as we can always easily create one in TIBCO Designer. But, before we go to why we need to use Java classes, we need to examine first the nature of an XML Schema. An XSD describes the XML document in a strictly structured manner, which means that the sequence and nesting of the elements are important. However, for JSON, we cannot rely on the order of the elements, and we cannot force JSON to be that way. It’s just its character, and it maintains itself as an unordered collection of zero or more name/value pairs. That said, we cannot expect a JSON message to conform to the sp
Read more

Using XML To Java in TIBCO BW

-
Image
There are cases when it is preferable to use Java code instead of XSLT when doing a complex string manipulation. For example, you would like to produce a single string from the different segments of an XML. You can do this by using XML To Java activity in TIBCO. Suppose you have the following XML: <?xml version = "1.0" encoding = "UTF-8"?> <Employees xmlns = "http://xmlns.tibco.com/javaschema/javaschema.Employees"> <Employee> <Age>24</Age> <Level>2</Level> <Name>Mark Cruz</Name> <Role>Technology Consultant</Role> <Skill>Java</Skill> <Skill>TIBCO</Skill> <Skill>Ruby</Skill> </Employee> <Employee> <Age>25</Age> <Level>1</Level> <Name>John Cruz</Name> <Role>Technology Consultant</Role> <Skill>TIBCO BW</Skill> <Skill>PHP</Skill>
Read more