EAI Mobile

Proper way to run a Bwengine on a 64Bits machine

First make sure your bwengine thats on your BW_HOME/bin isn't already a 64 bits.


/tibco/.../bin >file bwengine

bwengine: ELF-32 executable object file - IA64


As you can see "ELF-32" shows us that the file is a 32bits executable.


Please follow these steps to enable 64-mode for BW:


1) cp TIBCO_TRA_HOME/bin/wrap64 to BW_HOME/bin

2) Change directory to BW_HOME/bin

a. mv bwengine to bwengine32

b. mv wrap64 to bwengine

3) cp bwengine.tra to bwengine-bak.tra

a. Using a text editor, open bwengine.tra

b. Find all occurrences of IA64N and replace with IA64W

c. In the tibco.env.STD_EXT_CP property, find %RV_HOME%/lib/ and change it to %RV_HOME%/lib/tibrvj.jar

Tibco AppManage deployconfig error: RepoSecurityNotAuthorizeException: Can not read a node /

Hi,

Are you trying to use AppManage to upload a ear file or to do a deployconfig and you get the following error:
...
com.tibco.infra.repository.RepoSecurityNotAuthorizeException: Can not read a node /
....
Comand:
AppManage -config -deployConfig /test/myApp.xml -app $APP_PATH -user user1 -pw user1 -domain test

Make sure you are not making these mistakes:

- Using the correct application path on the appmanage comand line: AppManage -config -app $APP_PATH this $APP_PATH must be the same on you Administrator:
"$APP_PATH = BusinessProcesses/BillingCollect/XXX_BILLINGCOLLECT_01"

be careful with the first "/" , and create the application/upload the ear before you make a deployConfig.


- Please make sure you use the user witch as created the domain such as "admin" otherwise it will show this error message even if you have set full permitions on Administrator console.

Problems starting a ADB on HP-Itanium 64 - /usr/lib/hpux64/dld.so: Unable to find library 'libxerces-c2_164.so'

Hi,

have you run into this problem?

make sure you copy the file into the tpcl folder that's on ADB's tra!

#TIB TPCL Home
tibco.env.TPCL_HOME=/tibco/software/ae5/tpcl/5.5

you should run a "find . -name libxerces-c2_164.so" and find this file on /tpcl/5.4 or /tpcl/5.3 folder. Then copy it to the right folder.

If you don't find this file, make sure you ask for it to Tibco Professional Support, or give as a comment or send us a e-mail and we'll help you!

Support - ADB error message : [DataDirect][ODBC 20101 driver]1906072

Como este blog não foi feito só para as baboseiras do Daniel, aqui vai algo que pode ajudar muito pessoal:

Em Inglês pá estrangeirada:

As it can be seen on the title of the blog, we are a support team for a tibco project in Portugal.
Recently we came across a problem that was hard to determine as ours.
The message [DataDirect][ODBC 20101 driver]1906072 appeared on one of our adb.
After some investigating we determined that this is related with problems in the odbc.ini file.
So if you come across with something similar, please start by checking the odbc.ini file.

In adition:
On Unix machines, the Adapter error 20101 implies that your locale settings are not appropriately set (or) that the InstallDir parameter of the DSN named [ODBC] in the odbc.ini file does not point to the correct ODBC Home Directory.

To correct this situation, please follow the steps below.

1) Ensure that the property "InstallDir" of the Data Source named [ODBC] in the odbc.ini file has the right path to the odbc home directory (i.e. .../adapter/adadb//odbc).

2) Verify that your LANG and LC_MESSAGES environment variables are set to en_US or C. You can check this by typing locale at a shell prompt. If for some reason it must be set to a different value, you should create a symbolic link in the $ODBCHOME/locale directory with the same name as $LANG that points to the en_US directory. For example, if LANG=fr_CA.utf8, you would create a symbolic link called fr_CA.utf8 that points to en_US. For help on creating symbolic links see the man page for the ln command.

3) Verify that the user that the application using ODBC is running under has read/execute permission to the directory the message files are contained in ($ODBCHOME/locale/en_US/LC_MESSAGES). Also verify the user has read permissions to the message files themselves.

4) Verify the locale directory is located in the parent directory of the lib directory. In other words, make sure the locale directory is in the same directory that the lib directory is located in. (Both locale and lib directories should be under odbc home directory)

5) Run the below simple test to make sure the driver message files are being loaded. The below test is to login to the database using dbtest utility with invalid userid. After the last step of this test, make sure that the error message does not contain the number 20101.

a. Open a shell prompt and browse to the Adapter bin directory.
b. Issue the command $ . ./adbagent_env.sh

eg. [adainfy@accrdlnxas3 bin]$ . ./adbagent_env.sh

c. At the prompt, issue the following command and try to login to the Adapter database by providing an invalid userid.

$ dbtest /@

eg. [adainfy@accrdlnxas3 bin]$ dbtest testuser/wrongpassword@ODBCDSN



Hope this may be of use :)