Jms queue reciever is responsible for consuming the message 
from the JMS in a queue. While JMS queue requestor is 
similar to requset reply in soap. it waits fro a reply in 
reply/to queue.

SQL Direct Pallete

In call process we have an option as Process Name Dynamic
Override, this field is used to  determine dynamically 
which process to call when the process instance is
running.But here both the sub process should have the same
input,output and error schema.

If the installation folder of tibco will be in C directory
then once we have deployed the ear file ,the information
will be stored in the following location.

if domain name is mydomain and projectname is TestOne then

Log files  :
C:\tibco\tra\domain\mydomain\application\logs

TestOne.tra file :(it contains all properties) :

C:\tibco\tra\domain\mydoamin\application\TestOne

Service/Project :C:\tibco\tra\domain\mydomain\datafiles

First find the location where the custom palettes are
stored(You can change/get the path from
Edit/Preferences-user directories-User Palette directory of
designer window).Once you found the location simply copy
what are all the custom palettes you wish to use in other
project and paste the custom palettes directory in another
machine.
Note : If you are running two  projects in the same machine
then you need not do the above procedure .The custom
palettes will automatically available to the other project
which is running in the same machine.

By default custom palettes will store in  below location :
C:\Documents and Settings\username\.TIBCO\custom_palettes

A Job Shared Variable  allows you to store data for use by
each process instance. A separate copy of the variable is
created for each new process instance. This resource is
useful for passing data to and from sub-processes without
creating an input or output schema for the called process. 
You can use the Get Shared Variable and Set Shared Variable
activities to access the data instead of mapping data to a
called processes input or output schemas. New process
instances receive a copy of the variable, so data cannot be
shared across process instances.

Scope of the job shared variable is with in the process
instance i.e the values which was set in one process
instance ,can not be avaible in other process.
If job shared variable in Process definition-1  set to 5
then the same value will not exist in process definition -2
.This means a separate copy of instance is maintained in
each process instance.

String,Integer,Boolean,Password

There are two process variables that are available to all
activities that accept input: $_globalVariables and
$_processContext. $_globalVariables contains the list of
global variables defined on the Global Variables tab of the
project.  $_processContext contains general information
about the process, such as the process ID, the project name,
whether the process was restarted from a checkpoint, and so
on.This process Context variable will be created
automatically whenever we create an project

I believe this question might be framed wrongly.How many
types of variables are there in BW ?

		
ISO8859-1 (Latin-1)—Preferred encoding for projects that
deal only with English and other Western European languages
that belong to the ISO Latin-1 character set. If this
encoding is used for languages that do not belong to the
Latin-1 character set (such as Japanese, Arabic, etc.), data
loss may result.

	
UTF-8—Preferred encoding for projects dealing with languages
not belonging to the Latin-1 character set. This includes
most languages except for English and other western European
languages.