Editing Application Configuration
To edit an application’s configuration before or after deployment, do the following:
1. Expand Application Management > BusinessConnect > Configuration.
2. Click the BusinessConnect link in the Configuration Builder panel.
The Edit Application Configuration dialog contains the following tabs:
— BusinessConnect Tab, page 48
— General Tab, page 49
— Advanced Tab, page 49
BusinessConnect Tab
The BusinessConnect tab contains these additional sub-tabs:
• Public Process Configuration tab, page 48
• Private Process Configuration Tab, page 48
• Component Settings Tab, page 48 Public Process Configuration tab
Using this tab, you can configure public smart routing.
For more information, seeStep 3: Configuring Smart Routing, page 17.
Private Process Configuration Tab
Using this tab, you can select the transport type for communications between the TIBCO BusinessConnect server and private processes: TIBCO Rendezvous or JMS. Using this tab you can also configure the outbound File poller.
For more information, seeChapter 3, Private Process Configuration, page 27.
Component Settings Tab
Using this tab, you can configure TIBCO BusinessConnect components and configure some other advanced features, such as shared and large file locations.
From the Component Settings tab, you can open the following links:
• Intercomponent Communication, page 7
Editing Application Configuration
|
49• Intercomponent Advanced, page 8
General Tab
This tab displays information about:
• Application archive Package Name, Package Version, Package Description, Package Creation Date, and Package Owner.
• Application Parameters Name, Deployment Name, Description, Contact, Max Deployment Revision.
You can also use this tab to upload a new EAR archive file that contains a TIBCO ActiveMatrix BusinessWorks project.
• Click Upload New EAR File, and browse to the file location, and select it to upload.
Advanced Tab
This tab shows TIBCO BusinessWorks and Adapters Deployment Repository Instance.
TIBCO BusinessWorks and Adapters Deployment Repository Instance including the following information:
• Transport Transport is alwayslocal. No changes are required.
• Message Encoding Select UTF-8 or ISO
.
The Warning on this screen reminds you about the required version of the TRA agents on the target machines:
“Require TRA 5.3 (or higher) Agents on all target machines.”
50
|
Chapter 5 Manage the Interior ServerTracing
This section describes how to enable tracing and view tracing output in TIBCO Administrator, the TIBCO BusinessConnect engine, and the TIBCO
BusinessConnect palette.
Tracing for TIBCO Administrator
Enabling Tracing
To enable tracing, access the fileTIBCO_HOME\tra\domain\domain\
AdministrationDomain.propertiesand set the propertyLogDebug=true.
Viewing the Log
View tracing output in the logTIBCO_HOME\administrator\domain\domain\ logs\Administrator.log
Tracing for the TIBCO BusinessConnect Engine
Enabling Tracing for all TIBCO ActiveMatrix BusinessWorks Tasks
To enable tracing for all TIBCO ActiveMatrix BusinessWorks tasks:
1. Locate theBusinessConnect-Interior_Server.trafile in the
TIBCO_HOME\tra\domain\domain_name\application\BusinessConnect
directory.
2. Enable the task by editing the file as follows:
Trace.Task.*=True. 3. Click Save.
4. Deploy TIBCO BusinessConnect to apply this change.
Tracing affects the performance of a running TIBCO BusinessConnect engine.
Tracing
|
51Set log4j.logger.bw.logger property
1. locate the fileBC_HOME\lib\is\log4j.xml
2. Find the following line:
<logger name="bw.logger">
<level value ="INFO"/>
<appender-ref ref="tibco_bw_log"/>
</logger>
INFOis the default setting you can change it to DEBUG.
TIBCO LogLogic Integration
When you select DEBUG from log level, the details of the logs related to the transaction processing are traced. These logs are in a format that can be easily parsed and analyzed through TIBCO LogLogic. When these detailed logs are combined with the Gateway Server logs and the audit database, they provide an end to end view of the processing of a transaction. Below is a sample entry:
2017 Jun 30 13:02:51:577 GMT +0530 BW.BusinessConnect-Interior_Server Debug [bw.logger]
BW-EXT-LOG-300002
Job-4030.4030.B910EE33-F6C9-4EF3-BB3A-B5F188A89805.<machine
name>-t460-Interior-Server IBHTTPHandler.createAndSetSyncReply: HTTP message received. Returning HTTP 200
OK.
View the Log
You can view tracing output in the logs
TIBCO_HOME\tra\domain\domain_name\application\logs\BusinessConnect -Interior_Server.log
Enabling Verbose Tracing for TIBCO ActiveMatrix BusinessWorks Service Instances To enable verbose tracing for TIBCO ActiveMatrix BusinessWorks service instances follow these steps.
1. In the Configuration Builder window, click the hostname-Interior_Server link
52
|
Chapter 5 Manage the Interior ServerFigure 8 Editing Service Instance Dialog
2. Click the Process Configuration tab.
3. In the General section, select the Enable Verbose Tracing check box.
4. Click Save.
5. Redeploy and restart TIBCO BusinessConnect.
For more information, see TIBCO ActiveMatrix BusinessWorks Administration, section Changing Server Settings.
Enabling Tracing for the TIBCO BusinessConnect Palette
To enable tracing in TIBCO BusinessConnect palette, create a global variable
bc.palette.tracingand specify one of the following values:debug,error,
warn, orinfo. Indebug, you'll see every message on transport coming and going before dispatching to TIBCO ActiveMatrix BusinessWorks or before sending from TIBCO ActiveMatrix BusinessWorks.
On high volume and/or large messages in debug mode, performance will be heavily affected.
Production environments should set this property's value tononeor remove this global variable altogether. For verbose tracing (most of the comments are such), thedebugvalue is recommended.
Tracing is also self-describing as the palette reports the status of its tracing when initialized either from the designer or loaded runtime. If the property is not configured, the TIBCO BusinessConnect palette displays the name of the tracing property as well as the possible values that you can specify.
View the Log
There are two different contexts when using the TIBCO BusinessConnect palette:
• Design-time
• Runtime
Tracing
|
53During design-time, tracing output goes to thestdout.logfile of the folder set in Edit > Preferences > General > User Directories > User Log Directory.
During runtime, tracing output goes to the following locations:
• The project’s log file wherever the project was deployed
• The project’s log in the folder specified in the design-time setting when the project is run in the test-engine.
54
|
Chapter 5 Manage the Interior ServerChecking the State of the Interior Server Instance
1. Expand Application Management > BusinessConnect > Service Instances.
The Service Instances window appears.
2. View the state of the Service Instance.
• If the state isRunningand Status isOK, your service instance is up and running.
• If theStart successfully deployed servicescheck box was not selected inChecking the State of the Interior Server Instance, you can start theTIBCO BusinessConnectinstance by selecting the instance check box and clicking Start.
• To start, restart, stop, or kill any of the instances, select the check box next to the instance and click the appropriate button.
Starting and Stopping the Server
|
55Starting and Stopping the Server
In most cases you will start or stop the server as part of the deployment process.
To start or stop the server outside the deployment process, do the following:
1. Expand Application Management > BusinessConnect > Services Instances.
2. View the state of the Service Instance.
3. Select the check box next to the instance you want to start or stop.
4. Click Start or Stop.
Although the TIBCO BusinessConnect instance can be started from the command line, starting from within TIBCO Administrator is the recommended method.
56
|
Chapter 5 Manage the Interior ServerRemoving TIBCO BusinessConnect
Undeploying TIBCO BusinessConnect
To undeploy the TIBCO BusinessConnect application perform these steps:
1. Expand Application Management > All Applications.
2. Select the check box next to BusinessConnect.
Undeploybecomes active.
3. Click Undeploy.
4. Click OK.
Deleting TIBCO BusinessConnect
To delete the TIBCO BusinessConnect application perform these steps:
1. Expand Application Management > All Applications.
2. Select the check box next to BusinessConnect.
Deletebecomes active.
3. Click Delete.
A dialog box appears to verify that you want to delete the application.
Make sure that TIBCO Hawk agents are running on all target machines.
Hawk Microagents for Interior Server
|
57Hawk Microagents for Interior Server
The BusinessConnect engine implements a set of microagents to monitor and manage the various polling operations that happen inside the BusinessConnect engine.
Below are the microagent names and functions:
The most common reason for monitoring TIBCO BusinessConnect is for the FTP pollers. In an environment where there may not be reliable data connections to trading partners, there is a tendency for this poller to "hang" because of a bad connection to a SFTP trading partner. Using microagents, you can eliminate this issue with a Hawk rule and rulebase.
Server Name Description
SCHDTASKPOLLER Poller to look for scheduled tasks that need to be fired.
RESENDPOLLER Poller to look for transactions that need to be resent.
QUEUEACTIONPOLLER Poller to look for messages to send off the message queue (primarily batch transactions)
MDNPOLLER Poller to look for overdue MDNs with AS2.
InteriorController The main BC engine
HIBERPOLLER Poller to look up transactions that have hibernated too long
FTPPOLLER Poller that triggers inbound FTP inbound sessions on a periodic basis. This poller is vulnerable to hanging, so it would be good to monitor it.
CREDPOLLER Expired credential poller. Checks certificate store for expired certicates on a regular basis.
CANCELPOLLER Poller that looks at audit log for transaction that have been marked for cancellation. Primarily for RosettaNet and ebXML.
58
|
Appendix A Database Schema DefinitionAppendix A Database Schema Definition
To replace the deprecated Archiver Tool from the previous releases, details about Audit, Non-Repudiation and Runtime schemas are supplied in this appendix for users to create their own archiving strategy.
Topics
• Audit Schema Details, page 59
• Non-Repudiation Schema Details, page 100
• Runtime Schema Details, page 122
Audit Schema Details
|
59Audit Schema Details
Tables that are part of the audit schema are depicted inFigure 9.
Figure 9 Audit_RelationShip
For the schema above, the values are as shown inTable 16.
Table summaries for the audit schema are explained inTable 17.
Table 16 Audit_RelationShip Values
Name Value
Name Audit_RelationShip
Data Model Physical
60
|
Appendix A Database Schema DefinitionTable 17 Audit Schema Tables Summary (Sheet 1 of 8)
Name Documentation
BC_TRANSACTION
S This is the main table that holds all the summary rows for auditing. An audit trail happens when:
• TIBCO BusinessConnect sends or receives messages from a trading partner.
• TIBCO BusinessConnect Gateway engine bootstraps and starts up the event sources, as well as when BusinessConnect PartnerExpress or
BusinessConnect FTP Server users log in.
• TIBCO BusinessConnect PartnerExpress or TIBCO BusinessConnect FTP Server users, or other business protocol partners, transfer messages or receive messages to TIBCO BusinessConnect.
TheBC_TRANS_IDcolumn is aGUIDgenerated by TIBCO BusinessConnect that holds the latest transactionSTATUSfrom the partner or from the messages sent from the private process. TheSTARTDATEcolumn is stamped when the first entry is inserted, and theTScolumn is updated every time a child row is inserted in theBC_MESSAGEStable.
Depending on the business protocol type (such as TIBCO BusinessConnect EDI Protocol powered by Instream, TIBCO BusinessConnect Services Plug-in, TIBCO BusinessConnect ebXML Protocol, TIBCO BusinessConnect RosettaNet Protocol, TIBCO BusinessConnect SOAP Protocol) or the startup of the TIBCO BusinessConnect Gateway engines, various column values are populated differently in order to show the views differently when looked from the TIBCO Administrator UI. Usage of theAUXcolumns is completely governed by individual business protocols or Gateway instances, while the log viewer for individual plug-ins generates a screen layout based on the metadata of these plug-ins.
Users who archive theBC_TRANSACTIONSdata should query based on the
STATUScolumn and theTScolumn, which would give all the transactions between the dates specified for certainSTATUSes.
Note:This table will grow based on the exchanged transactions, as well as the number of times the Gateway instances are restarted.
This table should be added as a part of the archiving process; for example, a search forSelect * from BC_TRANSACTIONS whereSTATUSis such as
%COMPLETED% OR %ERROR%andTSis<from Date>.
Audit Schema Details
|
61A typical sample archive query for Oracle can be such as follows:
Select * from BC_TRANSACTIONS where STATUS in ('COMPLETED','ERROR') AND
TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD HH24:MI:SS.FF') <=
TO_TIMESTAMP('<to date>', 'YYYY-MM-DD HH24:MI:SS.FF') AND TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD HH24:MI:SS.FF') >=
TO_TIMESTAMP('<from date>','YYYY-MM-DD HH24:MI:SS.FF')
A typical sample archive query for Microsoft SQL database can be such as follows:
Select * from BC_TRANSACTIONS where STATUS in
('COMPLETED','ERROR') AND convert(datetime,convert(varchar, TS, 121), 121) >= convert (datetime, '<from_date>', 121) AND
convert(datetime,convert(varchar, TS, 121), 121) <=
convert(datetime, '<to_date>', 121)
(The query varies based on the database type) Table 17 Audit Schema Tables Summary (Sheet 2 of 8)
Name Documentation
62
|
Appendix A Database Schema DefinitionBC_MESSAGES This table provides an audit trail for each transaction summary row. The different state depends on the type of TIBCO BusinessConnect transaction, protocol, and plug-in variations that are used; it also varies based on the stage of transition a transaction enters, such as authentication, decryption, and so on:
• TIBCO BusinessConnect audit trails, startup activities, and transitions of each Gateway service in the Gateway Service Instance of the log in the TIBCO Administrator UI. It also audit trails the transaction exchange between partners and TIBCO BusinessConnect in the appropriate protocol level audit trail.
• Gateway Service Session login for user level activities for FTP Server and PartnerExpress are logged and an audit trail gets generated with
transitions.
• Business protocol level audits are captured and can be viewed in the appropriate Protocol Log Viewer section; for example, TIBCO
BusinessConnect Services Plug-in has its own Log Viewer screen that audits the different transitions the transactions go through when a partner sends or receives a message.
Various audit trail activities keep adding up and a table can grow significantly.
This table, along with its BIN table (BC_MESSAGES_BIN,BC_RESEND_BIN) should also be archived.
Usage of the AUXcolumns is completely ruled by individual business protocols or Gateway instances, while the log viewer for individual plug-ins generates a screen layout based on the metadata of these plug-ins.
Note:This table would grow based on the exchanged transactions, as well as the number of times the Gateway instances are restarted. This table should be added as a part of the archiving process.
Table 17 Audit Schema Tables Summary (Sheet 3 of 8)
Name Documentation
Audit Schema Details
|
63A typical sample archive query for Oracle can be such as follows:
Select * from BC_MESSAGES where BC_TRANS_ID IN (SELECT BC_TRANS_ID FROM BC_TRANSACTIONS where
TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD HH24:MI:SS.FF') <=
TO_TIMESTAMP('<to_date>', 'YYYY-MM-DD HH24:MI:SS.FF') AND TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD HH24:MI:SS.FF') >=
TO_TIMESTAMP('<from_date>','YYYY-MM-DD HH24:MI:SS.FF') AND STATUS IN ('COMPLETED', 'ERROR'))
A typical sample archive query for Microsoft SQL database can be such as follows:
Select * from BC_MESSAGES where BC_TRANS_ID IN (select BC_TRANS_ID FROM BC_TRANSACTIONS where
convert(datetime,convert(varchar, TS, 121), 121) >=
convert(datetime, '<from_date>', 121) AND
convert(datetime,convert(varchar, TS, 121), 121) <=
convert(datetime, '<to_date>', 121) AND STATUS IN ('COMPLETED', 'ERROR'))
The query varies based on the database type.
Table 17 Audit Schema Tables Summary (Sheet 4 of 8)
Name Documentation
64
|
Appendix A Database Schema DefinitionBC_MESSAGES_BI
N This table has a foreign key to theBC_MESSAGEStable. It contains certain transition details that TIBCO BusinessConnect logs, such as failure descriptions or payloads written by TIBCO BusinessConnect protocols when the option Include Message in Log is enabled.
Rows in this table need to be archived to avoid the table to grow too big.
Note:This table will grow based on the exchanged transactions for business protocols and should be added as part of the archiving process.
A typical sample archive query for Oracle varies based on the database type and can be such as follows:
Select * from BC_MESSAGES_BIN where BININDEX IN
(SELECT BININDEX FROM BC_MESSAGES where BC_TRANS_ID IN (SELECT BC_TRANS_ID FROM BC_TRANSACTIONS where
TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD
A typical sample archive query for Microsoft SQL database can be as follows:
Select * from BC_MESSAGES_BIN where BININDEX IN (SELECT BININDEX FROM BC_MESSAGES A, BC_TRANSACTIONS B where A.BC_TRANS_ID = B.BC_TRANS_ID AND convert(datetime,convert(varchar, B.TS, 121), 121) >= convert(datetime, '<from_date>', 121) AND
convert(datetime,convert(varchar, B.TS, 121), 121) <=
convert(datetime, '<to_date>', 121) AND B.STATUS IN ('COMPLETED', 'ERROR'))
Table 17 Audit Schema Tables Summary (Sheet 5 of 8)
Name Documentation
Audit Schema Details
|
65BC_ALERT This table has a foreign key to theBC_MESSAGEStable and contains Alert details that TIBCO BusinessConnect logs, such as expired certificates, and so on.
Rows in this table need to be archived to avoid the table to grow too big.
A typical sample archive query for Oracle varies based on the database type and can be such as follows:
Select * from BC_ALERT where BININDEX IN
(SELECT BININDEX FROM BC_MESSAGES where BC_TRANS_ID IN (SELECT BC_TRANS_ID FROM BC_TRANSACTIONS where
TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD HH24:MI:SS.FF') <=
TO_TIMESTAMP(<to_date>, 'YYYY-MM-DD HH24:MI:SS.FF') AND
TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD HH24:MI:SS.FF') >=
TO_TIMESTAMP(<from_date>,'YYYY-MM-DD HH24:MI:SS.FF') AND STATUS IN ('COMPLETED', 'ERROR')))
A typical sample archive query for Microsoft SQL database can be as follows:
Select * from BC_ALERT where BININDEX IN (SELECT BININDEX FROM BC_MESSAGES A, BC_TRANSACTIONS B where A.BC_TRANS_ID =
B.BC_TRANS_ID AND convert(datetime,convert(varchar, B.TS, 121), 121) >= convert(datetime, '<from_date>', 121) AND
convert(datetime,convert(varchar, B.TS, 121), 121) <=
convert(datetime, '<to_date>', 121) AND B.STATUS IN ('COMPLETED', 'ERROR'))
Table 17 Audit Schema Tables Summary (Sheet 6 of 8)
Name Documentation
66
|
Appendix A Database Schema DefinitionBC_RESEND_BIN This table stores all resendable information to be used by TIBCO
BusinessConnect. The stored messages are not in a readable format since it is proprietary information.
Note:This table will grow based on the exchanged transactions for business protocols and should be added as part of the archiving process.
A typical sample archive query for Oracle varies based on the database type and can be such as follows:
Select * from BC_RESEND_BIN where BININDEX IN
(SELECT BININDEX from BC_MESSAGES where BC_TRANS_ID IN (SELECT BC_TRANS_ID from BC_TRANSACTIONS where
TO_TIMESTAMP(TO_CHAR(TS,'YYYY-MM-DD HH24:MI:SS.FF'),'YYYY-MM-DD
A typical sample archive query for Microsoft SQL database can be as follows:
Select * from BC_RESEND_BIN where BININDEX IN (SELECT BININDEX from BC_MESSAGES A, BC_TRANSACTIONS B where A.BC_TRANS_ID = B.BC_TRANS_ID AND
convert(datetime,convert(varchar, B.TS, 121), 121) >=
convert(datetime, '<from_date>', 121) AND
convert(datetime,convert(varchar, B.TS, 121), 121) <=
convert(datetime, '<to_date>', 121) AND B.STATUS IN ('COMPLETED', 'ERROR'))
BC_UACLOG The tableBC_UACLOGlogs any edits that happen during the TIBCO
BusinessConnect configuration dome with TIBCO Administrator. All changes made by the user logged into the TIBCO Administrator UI are captured in this table. Any changes to participants, business agreements and operation editor are also part of the audit trail captured in this table.
The tablesBC_UACLOGandBC_UACLOG_DETAILcan be purged and archived based on the columnOPERATION_TIMEto be a part of the selection query.
Note:This table would grow based on the modifications to participants, business agreements, and operations. It should be added as part of the archiving process.
BC_LOGACL_TEMP This table holds the User-to-Partner information and is only transient until the user is logged and querying the log viewer.
Table 17 Audit Schema Tables Summary (Sheet 7 of 8)
Name Documentation
Audit Schema Details
|
67BC_DUP This table stores the transactions hash values, which are used to indicate whether an incoming or outgoing transaction is a duplicate. The information stored is completely controlled by individual business protocols.
Note:This table will grow as transactions are exchanged. It should be added as a part of the archiving process.
BC_UACLOG_DETA
IL Note:This table will grow based on the modifications to participants, business
IL Note:This table will grow based on the modifications to participants, business