Can I use the Developer tool to debug an adapter?
Yes. You can use the Developer tool to debug the adapter client components such as connection or metadata.
Navigate to the Developer client folder. For example,
C:\Informatica\version\clients\DeveloperClient.
Edit the
developerCore.ini
file and add the following Eclipse remote debug options:
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=portnumber
Launch the Eclipse IDE and create a
Remote Java Application
debug configuration.
Set the connection type as Standard (Socket Attach), and specify the host and port numbers to connect for debugging.
Launch the Developer tool.
Run the debug configuration in Eclipse after setting required breakpoints in the source files you wish to debug.
Can I use the Administrator tool to debug an adapter?
Yes. You can use the Administrator tool to debug the adapter server components.
From the Administrator tool, select the Data Integration Service from the navigator and click the
Properties
view.
Edit the
Execution Options
and set the
Launch Jobs as Separate Process
option to false.
Select the
Processes
view.
From
Service Process Properties
section, edit
Advanced Properties
.
Append the following Eclipse remote debug options to JVM Command Line Options:
-Xdebug
Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<portnumber>
Launch the Eclipse IDE and create a
Remote Java Application
debug configuration.
Set the connection type as Standard (Socket Attach), and specify the host and port number defined in the previous step.
Restart the Data Integration Service.
Run the debug configuration in Eclipse after setting required breakpoints in the source files you wish to debug.
What is the class-loading pattern of the third-party libraries in the Developer tool?
The Developer tool uses the OSGi-based framework for class loading. The Informatica Connector Toolkit adds the third-party libraries that the metadata class requires to the metadata adapter bundle class path. If the bundle class path is not in use in third-party libraries, analyze the class loading pattern and load classes to match the OSGi class loading pattern.
What is the class-loading pattern of the third-party libraries in the Data Integration Service?
The Data Integration Service uses a custom class loader and child first strategy to load the third-party libraries for the adapter. The Data Integration Service loads all the classes present in services/shared/* directories. Resolve conflicts if the Data Integration Service has loaded classes that conflict with the third-party libraries.
What must I do if I get the message asking me to check the JDK version even if JDK version 1.8 is installed on the machine?
In the Eclipse IDE, navigate to
and set
Compiler compliance level
to 1.8.
When I generate code for native metadata, I get an error message that project description files are out of sync with the file system. Does this error impact code generation?
No. This error does not impact code generation. If you still want to resolve this error, you can select the
Refresh using native hooks or polling
option from the
menu in the Eclipse IDE. If you choose to refresh using native hooks or polling, there may be considerable delay in generating code.
Is there a log file that I can refer when I encounter errors while I generate code or publish the adapter?
Refer to the <adapter_name>_codebuilder.log file for any errors that you encounter when you generate code or publish the adapter. The <adapter_name>_codebuilder.log file is available in the <Eclipse workspace>/<adapter project> folder.
Can I use the Informatica Connector Toolkit to upgrade an adapter?
Yes. The Informatica Connector Toolkit supports upgrade of an adapter. Use the
Upgrade
option in the
Publish Informatica Connector
wizard to reinstall or upgrade the adapter.
Can I use the Informatica Connector Toolkit to deploy an adapter on a worker node?
No. You must manually run the
installServer.bat
command to deploy the adapter on a worker node. The
installServer.bat
command uses the following syntax:
installServer infa_server_home upgrade skipregistration
infa_server_home
| Indicates the Informatica services installation directory.
|
upgrade
| True if you want to reinstall the adapter, false otherwise.
|
skipregistration
| True if you do want to skip registration of this adapter. Set this argument to true if you deploy an adapter on a worker node.
|
After I published an adapter, what must I do if I made changes only to the connection attributes, record extensions, field extensions, read capability, or write capability extensions?
If you added attributes, use the
Upgrade
option in the
Publish Informatica Connector
wizard to republish the adapter. The Informatica Connector Toolkit supports upgrade of an adapter only if the changes are additive. If you renamed or deleted any of the existing attributes, uninstall Informatica services, re-create the domain, and then install the adapter.
What must I do if the changes that I made to the run-time project are not reflected?
Shutdown the domain, delete the
work_dir
directory from <InformaticaServicesInstallationDirectory>/services, and then restart the domain.
What must I do if the Informatica domain is not available after I deploy the adapter?
Ensure that no Informatica services are running in the domain and then redeploy the adapter.
What must I do if the changes that I made to connection attributes or metadata attributes are not reflected in the Developer tool?
Run the
developerCore.exe
command with the
-clean
option.
How to enable a Cloud Data Integration connector developed using Informatica Connector Toolkit to use the proxy server?
Can I use the adapters built for Big Data Management to run on the Spark engine?
Yes. You can use the adapters built for Big Data Management to run on the Spark engine.
Do I make any changes to adapters built for Big Data Management to run on the Spark engine?
No. You do not have to make any changes to adapters built for Big Data Management to run on the Spark engine.
