Most of the Java based adapters used in PI run on AAE, the J2EE based adapter engine. However, in some cases it’s not possible to use the adapters as the platform doesn’t meet the prerequisites and in these cases adapters running on Java SE can be installed.

Link to standard documentation for adapters running Java SE.

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/6f/246b3de666930fe10000000a114084/content.htm?current_toc=/en/75/246b3de666930fe10000000a114084/plain.htm&show_children=true

These adapters can be installed on the remote hosts and can communicate with PI. The below diagram represents the installation. The host can be windows , unix etc.

 

One of the adapters is Extended File adapter also known as xlink adapter.

 

Configuring hundreds of windows hosts can be very difficult to maintain. However, we have an ABAP cockpit by which we’re able to maintain remote configuration. The information is stored in ABAP tables and gets synced to remote host by HTTP calls.

 

Recently we did migration of around 8000 interfaces from an older version of PI to PI 7.4 .

 

The information is stored as configuration files for xlink adapters as key value pairs.

 

We’re able to view the configuration from ABAP cockpit but there are two issues:

 

  1. Information is read by HTTP calls .So the xlink service needs to be up and running at the remote host. This is not the case during cutover from old to new system.

 

2) ABAP cockpit can display only adapter if we’re interested in reading adapter properties as it has to make a HTTP call for each adapter.

 

However we needed to

 

Table with the list of additional properties available in extended File adapter.

 

https://help.sap.com/saphelp_nw73ehp1/helpdata/en/29/ff067372cd4f44b6d6149101a1868c/content.htm

 

One of the main properties is the URL which determines to which PI system the message should be sent to.

 

 

We need a mechanism to verify the properties file after this property has been modified.

 

So we built a Java swing application that allows us to quickly read the properties.

 

The assumption is that the adapter properties file are stored in the below folder:

 

//f$//sap//xlink//XLi//Configuration where i is a running number starting from 0 for the xlink instance.

 

Active adapter are stored in folder //f$//sap//xlink//XL0//Data/ – this allows us to filter out any non-active adapters from our list.

 

The first tab has options to specify login credentials , chose adapter type to restrict searching them all and specify the attribute we want to read.

 

The second tab has 2 buttons:

  • Select file for processing : upload list of servers
  • Process to start execution

 

Once the file is chosen, the file name is displayed:

 

And the output appears in the below format.

 

The tool also allows us to export data as a CSV file.

 

 

Source code can be accessed at this link .

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply