A Frequently Asked Questions

FTP Adapter Does Not Publish or Subscribe to Messages

The FTP adapter is not publishing or subscribing to the messages.

Problem 1

The Transport properties of the FTP adapter might not be correct.

Solution 1

Specify 2 as the value of the log level parameter agent_log_level in the adapter.ini file of the FTP adapter. Restart the adapter and try to publish a message or subscribe to a message. You can see a log starting with TransportProperties.TransportProperties(). This log contains all the transport properties for the FTP adapter in the form of name value pairs. Ensure that the values of these properties are correct.

Problem 2

You might not have created a publish or subscribe event in iStudio for the FTP adapter that corresponds to the message structure. The FTP adapter is not able to match the message data to any of the events defined during design time and therefore cannot publish or subscribe the message.

Solution 2

Create a publish or subscribe event for the FTP adapter in iStudio corresponding to the message structure.

Problem 3

The FTP server is not based on RFC standards.

Solution 3

Ensure that the FTP server is based on RFC standards.

How do I know the FTP adapter has started properly?

View the log.xml file located in the timestamped subdirectory of the FTP adapter log directory:

If there are no exceptions, then the FTP adapter has started properly.

The FTP adapter did not start properly. What went wrong?

View the exceptions in the FTP adapter log file (log.xml). The exceptions should provide information about what went wrong. It is possible that the FTP adapter is unable to connect to the repository. Ensure the repository is started properly. The FTP adapter will connect to the repository once it is started properly. You do not need to restart the Adapter.

The FTP adapter is not starting. What could be the reason?

If you are starting the adapter for the first time or if you have set the agent_metadata_cache parameter to none or demand, then check if the repository is up and running. In addition, check if the hub database is up and running.

One reason can be that Oracle Wallet does not contain the password information corresponding to your application name. For example, during installation you defined the application name as myFTPApp. Later, you changed the application name in iStudio to FTPApp. In such case, you need to specify the password corresponding to the new application name FTPApp in the Oracle Wallet. You can create password by using the oraclewallet command.

Is it possible to edit the FTP adapter configuration settings created during installation?

Yes, edit the parameters in the adapter.ini file in the following directory:

When I change an element in iStudio, such as mappings, it seems like the FTP adapter is using old information. What is happening?

The FTP adapter caches information from iStudio. The information is stored in the repository locally. If you change something in iStudio and want to view the change in the runtime, then you need to stop the FTP adapter, delete the FTP adapter cache files, and restart the FTP adapter.

The FTP adapter has a persistence directory which is located in the FTP adapter directory. Deleting this directory when the FTP adapter has been stopped should make it obtain the new metadata from the repository when started.

How do I secure my passwords?

OracleAS Integration InterConnect uses Oracle Wallet Manager to maintain system passwords. When you install OracleAS Integration InterConnect, Oracle Wallet Manager is also installed and a password store is created. All passwords used by OracleAS Integration InterConnect components are stored in the password store. The password is stored in the Oracle Wallet in the following format:

ApplicationName/password

The ApplicationName is the name of the application, which is extracted from the adapter.ini file of the corresponding adapter. In the adapter.ini file, the application parameter specifies the ApplicationName to which this adapter connects. The password for the application is also retrieved from the adapter.ini file.

The number of entries is dependent on the type of adapter. For example, Database adapter needs two entries whereas AQ Adapter needs only one entry. The following table lists the entries that will be created for each adapter:

You can create, update, and delete passwords using the oraclewallet command. When you run the command, it prompts you for the admin password.

You can use the following commands to manage your passwords:

• List all passwords in the store

  oraclewallet -listsecrets
  
  

• Create a password

  oraclewallet -createsecret passwordname
  
  

  For example, to create a password for the hub schema:

  oraclewallet -createsecret hub_password
  
  

• View a password

  oraclewallet -viewsecret passwordname
  
  

  For example, to view the password for the hub schema:

  oraclewallet -viewsecret hub_password
  
  

• Update a password

  oraclewallet -updatesecret passwordname
  
  

  For example, to update the password for the hub schema:

  oraclewallet -updatesecret hub_password
  
  

• Delete a password

  oraclewallet -deletesecret passwordname
  
  

  For example, to delete the password for the hub schema:

  oraclewallet -deletesecret hub_password
  
  

How can I deliver a message to a specific partition of the publishing FTP adapter?

Scenario: FTP adapter has two partitions PAR1 and PAR2. You want to deliver event create_customer to partition PAR1 and add_customer event to partition PAR2.

Perform the following tasks:

1. Assign event create_customer to partition PAR1 and event add_customer to partition PAR2.

2. Create two directories. For example, DIR1 and DIR2.

3. Configure the adapter with partition name PAR1 to poll DIR1 and adapter with partition name PAR2 to poll DIR2.

4. Publish the message for event create_customer to DIR1 and the event add_customer to DIR2.