TIBCO BUSINESS WORKS VIDEOS

Bouncing the Administrator

Steps to be followed on Unix Machine:

1). Check whether the hawk agent is running in the all the machines or not.

Command for checking in each different machines

ps -ef|grep hawk

2.Check the log

cd /opt/tibco/tra/domain/<Domain_Name>/logs

3.Check the log using

vi hawk.log

4.Check the admin machine and verify the log of the admin machine

5.Copy the log to the ps pad as a back up in case some one asks for the reason why you bounced the administrator.

6.Kill the hawk agent of the adminstrator machine

kill -9 pid (hawkagent)

7.Kill the adminstrator of the admin machine

go to

cd /opt/tibco/administrator/domain/<Domain_Name>

kill -9 ./tibcoadmin_<Domain_Name>

8.Restart the admin of the administrator

nohup ./tibcoadmin_<Domain_Name> &

9.check whether the administrator is running or not by verifying in GUI of the admin or by using the ps -ef|grep admin command.

10.Restart the hawk

nohup ./hawkagent_<Domain_Name> &

11.Verify whether the hawk is running or not

ps -ef|grep hawk

Please send us your comments.

Bouncing the Administrator

Steps to be followed on Unix Machine:

1). Check whether the hawk agent is running in the all the machines or not.

Command for checking in each different machines

ps -ef|grep hawk

2.Check the log

cd /opt/tibco/tra/domain/<Domain_Name>/logs

3.Check the log using

vi hawk.log

4.Check the admin machine and verify the log of the admin machine

5.Copy the log to the ps pad as a back up in case some one asks for the reason why you bounced the administrator.

6.Kill the hawk agent of the adminstrator machine

kill -9 pid (hawkagent)

7.Kill the adminstrator of the admin machine

go to

cd /opt/tibco/administrator/domain/<Domain_Name>

kill -9 ./tibcoadmin_<Domain_Name>

8.Restart the admin of the administrator

nohup ./tibcoadmin_<Domain_Name> &

9.check whether the administrator is running or not by verifying in GUI of the admin or by using the ps -ef|grep admin command.

10.Restart the hawk

nohup ./hawkagent_<Domain_Name> &

11.Verify whether the hawk is running or not

ps -ef|grep hawk

Please send us your comments.

You can stop Hawk agent/ uninstall all tra components in that machine, login into tibco Administrator and select the machine and click on the option remove. It removes it from the domain. Hope this info helps.

If you need to change password for admin user in TIBCO Administrator please keep in mind that it is not enough just to change the admin password from Administrator GUI. But whole procedure is not so complex.

Always have full backup of Administrator configuration files and repository files or database!Change admin password in the Administrator GUI.Start DomainUtility on each machine in the TIBCO Domain, select Server Settings => Update Domain Credentials and change password there or use domainutilitycmd and ChangeDomainCredentials.xml as a template.Make sure that password has been changed in tibcoadmin_<domain>.tra file. Or you can put new password manually there like this repo.securePassword=#!tibco and use obfuscate utility to encrypt it.Restart Administrator daemon and Hawk Agents everywhere in TIBCO domain.That’s all. But, if you change password in the Administrator GUI only, and Administrator service (on the Windows) or daemon (on the Unix) has been restarted as nothing is working as before, then you can find picture like this on your screen when you try to login into Administrator. If your daemon has been started using nohup utility as mine, then you have a chance to find little more in the nohup.out file:

com.tibco.infra.repository.RepoSecurityException: Can not read policy domain for repository server HM : Failed in authentication.

If you start DomainUtility at this time and try to change password there, following error will appear.

To solve this problem you need to disable security option in the tibcoadmin_<domain>.tra file

#repo.isSecurityEnabled=true

repo.isSecurityEnabled=false

then restart Administrator.

Now it is possible to continue the procedure from step 3: DomainUtility will work. When password will be changed, you can enable security back in tra file. Do not forget to restart Administrator daemon and Hawk Agents everywhere in the domain!

After all, redeployment of all applications may be necessary.

To Delete a Domain Using the GUI:

1. If more than one machine belongs to the domain, you must first remove each

machine from the domain or your environment will be inconsistent.

2. Shut down the TIBCO Administration server and the TIBCO Hawk Agent for

the domain. On Microsoft Windows, navigate to the Services panel and stop

the two services for the domain to delete.

3. Start Domain Utility and click the Next button on the main screen.

4. Under Category, click Domain Configuration, then click Delete an

Administration Domain.

5. Click Next and in the screen that appears, select the administration domain to

delete.

6. Provide the administration domain user name and password.

7. Click Show Advanced and clear the check box next to Delete Application

Domains, if you want to keep them.

8. Click Next and read the warning that appears.

9. Click Next to remove the domain.

10. Click Finish to end the session.

To Delete a Domain Using the Command Line Utility :

1. Create a working directory that will hold the XML file that defines

configuration options.

2. Copy the following file to your working directory:

TIBCO_TRA_HOME\template\domainutility\cmdline\DeleteDomain.xml

3. Open DeleteDomain.xml in a text editor.

After changing the parameters, save the file and exit the text editor.

4. Execute the following command on the machine on which the secondary

server has been installed:

domainutilitycmd -cmdFile

working-dir-path\DeleteDomain.xml

IBCO domain needs a repository where all service data are stored. This repository can be in xml files near TIBCO Administrator or it can be in a database. When you run both master and secondary servers of TIBCO Administrator, it is better to store repository in a database, because if it stored in files, both Administrator instances have to maintain its own copy of the repository. So, it could be a problem with syncing in some cases. When the copy of repository on the secondary server is out of sync, we can experience a problem with deploying and starting applications.The errors seen in the admin log file:

2010 Feb 15 13:24:21:267 GMT +4 Error [ApplicationConfiguration] AESDKJ-0000 [http-8090-Processor11] COM.TIBCO.hawk.talon.MicroAgentException: Request timed out

2010 Feb 15 13:24:23:720 GMT +4 Error [Administrator] AESDKJ-0000 [http-8090-Processor11] ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error

And in the tsm log files errors are similar to:

2010 Feb 15 13:23:10:335 GMT 4 tsm Debug [] [TRA-000000] tsm.syncBindings: probably admin server is not available. exception message: com.tibco.pof.entity.EntityStoreException: error creating client Server not responding

Caused by: com.tibco.infra.repository.OperationFailedException: error creating client Server not responding at com.tibco.infra.repository.RepoFactory.newClient(RepoFactory.java:3046)

Workaround is to stop secondary Administrator and deploy then. Solution is to stop secondary Administrator, remove all repository files on the secondary server, then copy repository files from the master. Usually all repository files in the <tibco_home>\administrator\domain\<domain_name>\data folder. Strategic decision – migration to a database storage.

By the way, when you plan a backup/restore solution, it makes sense to backup repository only on the master TIBCO Administrator, but in the case of recovery, restore it on both at the same time.

IntroductionThis article describes the differences between the two types of domain data storage that can be used:

FileDatabaseNote that there are two types of transports available to a domain:

RVEMS. If this option is chosen for domain transport then a database must be used for domain storage.Setting the Domain Storage TypeThe decision to set the storage type is made when the domain is created.

Using the Domain Utility GUIThe checkbox highlighted below determines whether database or file storage is used.

After this checkbox is selected, a later screen will gather the database connection details and provide the opportunity to test the database connection.

Using the Domain Utility command line executable (domainutilitycmd)To create a database based domain, the following section of the CreateDomain.xml file should be uncommented (the “<–” and “–>” markers removed) and filled in as appropriate. If a file based domain is to be used, then this section should be left commented.

<!– uncomment the following for DB configuration –><!– <DatabaseConfiguration>

<DatabaseUrl>jdbc:tibcosoftwareinc:sqlserver://localhost:1433;databaseName=eaidb </DatabaseUrl>

<DatabaseUsername>sa</DatabaseUsername>

<DatabasePassword>sa</DatabasePassword>

<JdbcDriver>tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver</JdbcDriver>

<DatabaseMinConnections>0</DatabaseMinConnections>

<DatabaseMaxConnections>5</DatabaseMaxConnections>

</DatabaseConfiguration>

–>

File Based DomainAs the name implies, the domain data is stored in the files on a system drive.

Warning: Although these files are written in XML, they should not be manually edited as that can cause corruption of the domain rendering it inoperable.

Location of FilesBy default these files are stored in the directory:

<TIBCO HOME>/administrator/domain/<domainName>/data

However this can be altered when the domain is created.

Using the Domain Utility GUIOn the “Create New Domain” task, check the “Show Advanced” box

Then scroll down and set the Domain Home values as required.

Using the Domain Utility command line executable (domainutilitycmd)The CreateDomain.xml file can be altered to set the domain home files as needed by setting the following XML parameters.

<TRADomainHome/> <AdminDomainHome/>

The following table provides some details regarding the different files that may be found in this directory:

File NameDescriptionSYS_<domain name>.datThis file contains details of the applications deployed,deployment history and plugins used.AUTH_<domain name>.datThis file contains the domain access control data: users, roles, and the permissions associated with them.SYS_PJBtemp.dat.filesThis directory contains binary data for the domain. Note that this directory contains subdirectories with names like:plicationConfiguration ationConfiguration

This is by design. There is an FAQ regarding this – FAQ1-9DCF6M

Other files may also be found in this directory some example are belowAPP_<domain name>_HawkConfig.datData linked to domain plugins.APP_<domain name>_MonitoringManagement.datAPP_<domain name>_Uddi_App_Domain.dat<domain name>-<Application name>.datData associated with a application deployed on the server (where the application transport is either HTTP or RV)<domain name>-<Application name>.dat.filesBenefitsIt is not database dependentLimitationsWhen Administrator starts up, the entire SYS and AUTH dat files are read into memory. If there are a large number of deployments or a large deployment history then this can slow down the Administrator upon start-up. This can be worked around by ensuring the application deployment histories are kept to a minimum. However it does limit the number of applications that can effectively be deployed.During deployment, the entire SYS dat file is rewritten a few times which could potentially slow down deployment.A domain update (including deployments) means that the whole dat file (SYS, AUTH or both) has to be rewritten to disk. This means there is the possibility of corruption if there is a write or disk failure.Database Based DomainThe domain data is stored in a database.

The exact database schema depends upon factors such as the plugins that have been installed and the type of password policy used. Hence the schema is not publicly available and the database user must have permission to create new database objects.

Steps as follows :

1) Login to Tibco Administrator.

2) Application Management->Application Name->Configuration->Process archive.par->Monitoring tab->Add Event.

3) Application Management->Application Name->Configuration->Adapter Configuraion.aar->Monitoring tab->Add Event.

4) Resource Management->Machines->Configure Monitoring->Edit->Add Event.

Note : There is option in the add event, if you want to get the alerts multiple occurences, you can choose the  radio button as multiple.

There are three main kinds of adapters supported by TIBCO:

1) Technical Adapters:- These adapters target a specific technology that represents all similar types.

For Example:

a) File Adapter:- represents many the file types including Text, XML, CSV, etc.

b) Databade Adapter:- represents many database types including DB2, Sybase, Microsoft MySQL, etc.

2) Functional Adapters:- These adapters target a specific individual Application.

For Example:

a) People Soft Adapter.

b) Adapter for Oracle Financials.

c) Seibel Adapter.

d) SAP R3 Adapter, etc.

3)Custom Adapters:- These are the adapters that we explicitly write code for.