Guru Of Geeks

Superior performance over competing drivers - DataDirect Connect for ODBC wire protocol drivers offer significant advantages over native ODBC programming. Advantages of Using ODBC / Wire Protocol Drivers Disadvantages of Native Programming Faster than native programming Using DataDirect  wire protocol  drivers results in faster application performance than coding to the native database API. This is possible because DataDirect drivers include many performance features such as network optimization. For example, DataDirect uses compressed data packets that are allowed by the architecture of our drivers, but not by the native interface the database uses. This means significantly fewer packets are transmitted across the wire, resulting in better application performance. In addition, DataDirect drivers don't use database client libraries to communicate with the database as other drivers do, instead accessing it directly through the database's wire protocol. This eliminates the extra ...

Pre-requiste for Integrating LDAP with Tomcat: Operating System : Windows with Active Directory 2003 and above Java : Jdk 1.6 and above Application Server : Tomcat 6.0 and above Populate LDAP We will set the security to permit a specific group of users to access Webapps Deployed. This group needs a name, which is configured within LDAP. You may already have an appropriate group. Create users in Active Directory for Application to validate. Create a group eg: TomcatUsersGroup and Associate users with this group in Active Directory using the wizard. Configuring Tomcat to Use LDAP Next, we need to configure tomcat to connect to ldap. This is specified in this document : http://tomcat.apache.org/tomcat-6.0-doc/realm-howto.html#JNDIRealm This is the difficult step. It requires adding an entry to  server.xml , found in the  conf  folder for Tomcat. For our example, the entry is as follows: Comment the following lines in the server.xml: <!– <Realm className="org.apache.catalina.rea...

Problem(Abstract) After adding a new parameter to an existing Parameter set, DataStage job fails with the error: Controller problem: Error calling DSSetParam(PARAM_SET.$PARAM),code=-3 Symptom After adding a new parameter to an existing Parameter set, Information Server job fails with the following error: "Controller problem: Error calling DSSetParam(PARAMETER_SET.$PARAM_NAME),code=-3  [ParamName does not reference a known parameter of the job]" Cause The reason for this type of issue is usually there is a mismatch of the parameter set list used by sequence and its jobs. Essentially a Parameter Set is a design-time object which provides a shorthand for a list of parameters so that the same list can be used in  multiple places.  Job compilation takes a snapshot of the job design and related objects and generates a job executable which is based on the state of those  objects at compile time.  For example, if Sequence job and a job both uses the parameter set. Adding a parameter ...

Problem(Abstract) When you import very large amounts of metadata by using connectors in InfoSphere Metadata Asset Manager, imports can fail with "session time out" or "out of memory" errors. This can happen at varying stages of the import. Symptom The import might fail in the following ways: During the import to staging area, with one of the following messages: " Failed to receive response from the handler. Request timed out. " " Java heap size/Out of Memory " During the preview stage, with a session timeout or out-of-memory error. While sharing to the repository, with a session timeout or out-of-memory error. You can determine the type of error by viewing the  SystemOut.log  or  messages.log  of IBM WebSphere Application Server. For example, the default location for  SystemOut.log  is "IBM\WebSphere\AppServer\profiles\InfoSphere\logs\server1"  and  messages.log  is "IBM\InformationServer\wlp\usr\servers\iis\logs"  (this is va...

I have recently upgrade my BPM Std environment to BPM 8.5.6. When trying to start the deployment manager after the upgrade I see the following exception on the commandline ./ startManager . sh runConfigActions script execution failed .   Exit  code :   1 Exception  caught  while  waiting  for  runConfigActions script to complete : /opt/ ibm / BPM / v8 . 5 / profiles / DmgrProfile / bin / runConfigActions . sh After upgrading to 8.5.6 and starting the servers for the first time some automatic post upgrade steps are executed. The error message indicates that there is an issue running those automatic steps. The logs to check in that case are BPMConfig_.log in the profile's log directory and bootstrapProcessServerData.log (only for the deployment manager) In that specific case here the following exception showed up in the bootstrap log: ImportFileHel  E  PreparedStatementCallback ;  bad SQL grammar  [ select  SNAPSHOT_ID , CREATED_ON , NAME , ACRONYM , DESCRIPTION , SEQ_NUM , ERROR_COU...

​ For any Connector Metadata import user needs to restart the Node agent after setting all the required parameters of a connector. For DB2 Connector we can do MDI (Metadata Import) using below steps Steps to setup DB2 environment prior to import (Please use root user for below steps) 1)    Install DB2 Client/Server on Information Server machine 2)    Set the DB2 related environments like DB2INSTANCE, LD_LIBRARY-PATH/LIBPATH, PATH using one of the below steps Source db2profile, it can be done by below command  source /home/db2inst1/sqllib/db2profile   (Where /home/db2inst1 is DB2 Home) OR Add the below parameters in dsenv PATH=/home/db2inst1/sqllib/bin:$PATH export PATH LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib:$LD_LIBRARY_PATH     export LD_LIBRARY_PATH               DB2INSTANCE=db2inst1 export DB2INSTANCE Now source dsenv and restart the DSEngine. *db2inst1- Instance name of DB2 Client/Server *LIBPATH needs to use for AIX instead of LD_LIBRARY_PATH ​ ​ 3)    Source dsenv, it can be do...

How to configure linux samba server step by step guide Example and Implementation Most Linux systems are the part of networks that also run Windows systems. Using Linux Samba servers , your Linux and Windows systems can share directories and printers. This is most use full situation where your clients are window native and you want to use the linux security features. Exam question There are mixed lots of System running on Linux and Windows OS. Some users are working on Windows Operating System. There is a /data directory on linux server should make available on windows to only vinita should have right to connect with samba server . Configure to make available. Configure samba server In this example we will configure a samba server and will transfer files from client side.For this example we are using two systems one linux server one window clients. per quest of samba server A linux server with ip address 192.168.0.254 and hostname Server A window client with ip address 192.168.0.2 and...