TIBCOAdmin-domain_name windows service does not start

Installation of TIBCO Administrator 5.9.1 on a Windows Server 2008 R2 Standar.

The administration domain creation process has added a service called "TIBCOAdmin-DomainName".
 
When we try to start the service "TIBCO Admin-MINISDEF SOA_DES", the service doesn't start completely and the service stays on "starting" state. And of course, TIBCO Administrator server doesn't start.

By other side, if we execute "domain/domain_name bin/tibcoadmin_domain_name.exe" from console then the TIBCO Administrator start successfully.

Solution:

Update the NT service using below command using command line,please run cmd as administrator.

<TIBCO_HOME>\administrator\domain\<DOMAIN_NAME>\bin\tibcoadmin_<Domain_Name>.exe

--update

TIBCO BusinessWorks. Sample 1: Global Variables and Properties Files

A BW X process invokes n times to another process BW Y. The number of times the process X calls the process Y is set in a global global variable whose value is set in the property file.

Steps:

1.    Create a BW project
             a.    Create a folder “VariableGlobal_FichProp”
             b.    Start TIBCO Designer
                        i.    Create a new BW project

                       ii.    Select the forder you have created before

                       iii.    Click “OK”

2.    Create the global variable “n” whose value will be set in the property file:
                  a.    Select the tab “Global Variables” in IBCO Designer and open the editor clicking on the icon:

             
                      b. Add the group variable “ejemplo1” clicking the icon

                      c.    Inside the group create the variable “n” clicking on "abc" icon. Set   “_PROPFILE_” as text value for the variable. This value indicates that the value of the variable is obtained from a properties file.

                           Click on OK

                     d.    In the “VariablesGlobales_FicherosPropiedades” folder, add a new definition process. Set “Proceso_VariableGlobal_FichProp” as process name and click “Apply”.

                       e.    doble click over the process definition.

                      f.    Create a process variable “i”.
                                  a.    In the section “Process Variables”
                                  b.    Asign the value “i” to the field “name”
                                  c.    Add the integer element “i”
                                  d.    Apply and save

                      g.    Add a task “WriteToLog” from the “General Activities” pallete

                              With this taks the console will show the number of itarations.

                              a.    Configura the task “Log”. Assing to the “message” field the value “concat(“i: “,$i/i)” through the formula editor. Click in the icon

                  h.    Assing a initial value to the variable “i” using the task “Assing” from the  General Activities pallete.
                              a.    Create the “Assing” activity (General Activities  Assing)
                              b.    Slect i into “Process Variable to Set”
                              c.    In the “input” tab asigns the value 0 to the variable “i”

                             d.    Click on “Apply”
                 i.    Create a group for the task "Log". Select the “Log” activity and click on the create group icon. 

                             a.    Click on the group icon and select “Repeat-Unti-True”.
                             b.    Set the “Index Name” field with the value “j”
                             c.    Complete the field “condition” with “$i/i=$_globalVariables/pfx:GlobalVariables/ejemplo1/n”. Do this with the formula editor.
                             d.    Press “Apply”

               j.    Configure the log task like the image below.

               k.     Add a new asing activity to add 1 to the variable i.

                              a.    In the “Input” tab add 1 to the precess variable i. Asign the value $i+1.

            l.     Create the propeties file “bwprop-VariableGlobal_FichProp-DEV.prop” in “<dir_home>/CursoTIBCO/configuracion”. Use the file explorer to to this. 

                         a.    Open the file with a text editos and add the next text:

#
# Properties file
#
# Configuration sample 1
#
##########################################################
# Variables
##########################################################
tibco.clientVar.ejemplo1/n=10

                          b.    Save



              m.     To test the sample fo to the Test tab in TIBCO Designer.
                           a.    Click on the icon “Star testing”
                           b.    Select the process “Proceso_VariableGlobal_FichProp”
                           c.    for reference the properties file click on “Advanced” and add the line “-p <dir_home>/CursoTIBCO/configuracion/bwprop-variableGlobal_FichProp-DEV.prop” in the field “Test Engine User Args”.

                         d.    Press “Load Selected”
                         e.    Open the console: Window  Show Console
                         f.    The console shows the fianl log:

2010 Jun 15 17:14:37:890 GMT +2 BW.FormacionAvanzadaBW Info [BW-Core] BWENGINE-300002 Engine FormacionAvanzadaBW started
2010 Jun 15 17:14:39:334 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 0
2010 Jun 15 17:14:40:017 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 1
2010 Jun 15 17:14:40:702 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 2
2010 Jun 15 17:14:41:468 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 3
2010 Jun 15 17:14:42:143 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 4
2010 Jun 15 17:14:42:866 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 5
2010 Jun 15 17:14:43:544 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 6
2010 Jun 15 17:14:44:228 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 7
2010 Jun 15 17:14:44:988 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 8
2010 Jun 15 17:14:45:663 GMT +2 BW.FormacionAvanzadaBW User [BW-User] - Job-1 [Ejemlos/VariableGlobal_FichProp/Proceso_VariableGlobal_FichProp.process/Group/Log]: i: 9

TIBCO BusinessWorks. Global Variables and Property Files

3.1    Global Variables

3.1.1    Description

Global variables provide a simple tool to set defaults values for use throughout the BW project. These variables are defined in the "Global Variables" tab in the TIBCO Designer project view.

When you want to use a global value at runtime as a resource must use enclosed with "%%" (without quotation marks) on both sides.

When you create a global variable, you can specify the following attributes:

• Name: Provides a name for the variable.

• Value: Provides a default value of the variable.

• Deployment: It makes visible the variable from the TIBCO Administrator.

• Service: Indicates that the variable should be included when the "Include all service level Global variables" is checked when the file is created ".ear". This option is used for file TIBCO adapters.

• Type: Select the type of variable, String, Integer, Boolean or password.

• Restriction: Gives String/Integer chains and an allowed range.

• Description: Provides a description of the variable.
The contents of global variables can be modified before deploying the application from the TIBCO Administrator.

You can also specify the values of global variables in an application running in a process engine from the command line. For this you use the following parameter in the BW engine start:

-tibco.clientVar.<variablePathAndName> <valor>

•  variablePathAndName: the variable name (including the path to the variable if placed in a folder or subfolder).
• value: is the value you want to set to the variable.
For example, if you have a global variable name item1 in a folder named myGroup and want to set its value to 500, add the following line as parameter in the BW engine start, and the value will be charged on the engine start process:

-tibco.clientVar.myGroup/item1 500

3.1.2   Use cases

2 uses are contemplated in this section:

• Resource Configuration (HTTP connections, JMS connections, etc.)

• Input values for BW tasks.
Global variables are read-only values that are initialized at the start of BW engine. The values of global variables can change or not change in different environments where the application through TIBCO Administrator is deployed. You can change the Global Variables' value through a parameter in the engine starting from BW or file properties

Global variables are used to reference values:

• Resource Settings. Eg: ftp connections, configuration of URL in SOAP tasks for invoking services, etc.

• Input Bindings. Input fields on the tasks that form a BW process.

Global variables facilitate code maintenance of our application, but the ultimate goal is to facilitate configuration changes and changes in the application environment. Through global variables a configuration change or a change of environment does not require a modification of the code, application packaging and deployment. You only need to change the value of global variables and stop and restart the engine of BW.

Global variables are often used in the following situations:

• Set the environment settings
• Tuning or Performance Settings
• Setting resources or services
• Setting constant references to external systems

3.1.3   Changing global variables

Global variables defined in a project can be modified in the following ways:

1. Using TIBCO Business Works Designer at design time.

2. Using TIBCO Administrator at deployment time.

3. Using properties files at runtime engine stopping and starting BW.

4. In command line stoping and starting the BW engine.
Take into consideration that same global variable can be applied a value of four ways simultaneously. In this case, the value that prevails is the command line, followed by the value in the property file, then indicated in TIBCO Administrator and finally the configured with TIBCO Designer.

This paper describes and details Option 3 as part of the Best Practices of Business Works. Using the properties files limits the use of TIBCO Administrator tool change as global variables.

3.1.3   Using properties files in TIBCO BusinessWorks

We recommend using a properties file per project to organize global variables, and thus set a naming convention for naming files. The following convention is recommended:

bwprop-<project name>-<environment>.prop

When the value of a global variable is set by properties file is recommended to give the value "_PROPFILE_" at design time by TIBCO Designer to indicate this fact and to avoid misuse.

The properties files are listed in the project file .TRA generated by TIBCO Administrator. The .tra file is modified as follows:

tibco.env.APP_ARGS=-p bwprop-<nombre proyecto>-<entorno>.prop -p bwprop-<nombre proyecto>-<entorno>-config.prop

The .tra files of different projects are in the domain where they have been deployed.
/tibco/tra/domain/<nombre_dominio_tibco>/application/<nombre_despliegue>

WARNING: The deployment of the project regenerates the .tra file and the changes made using the properties files will be lost.