Using Integration Directory Programming Interface Error Wrong_Version

Hi all
using the IB API to query and read the objects in the pi 7.11 I get the error wrong_version
by reading of some interface determinations.
If I use the webservice InterfaceDeterminationQuery all will worke fine but using
InterfaceDeterminationRead some of the interface determinations response WRONG_VERSION
All Objects are from PI 7.11 and the wsdl File are from SAP BASIS 7.11
any idea?, testingteh same from the WSNavigator in the pi will work fine.
regards
Ralf

Hi Ralf, did you solve the problem? Are there any detailed error messages/payloads/stack traces? Thanks, regards, Martin

Similar Messages

Problem in creating Receiver Agreement using Integration Directory API

Hello Experts,
We are developing a scenario where we are creating "REceiver Agreement" through Integration Directory API.
This requires certain parameters like Sender component, Interface, Communication Channel & Namespace to be set in the code.The required Communication Channel & Components already exist in Integration Directory .
Our concern is that we are not able to retreive this Communication Channel's ID through the code in order to set it as a parameter for Receiver Agreement generation.
Can anybody pls advice??
Thanks in advance,
Suraj.

Hi Stefan,
We tried using query on communication channel, but could not do it as we could not get a method which accepts name of communication channel as parameter.
We used "CommunicationChannelQueryIn" related methods in the API.
But still could not retreive the Communication Channel ID of an existing Communication Channel.
Please help.

Generating WSDL using Integration Directory (Tools-Define Web Service)

Hi,
I have tested the "Define Web Service" tool in Integration Directory - some question;
1) It's a little bit frustrating to change the URL after clicking the "Propose URL" button - is it possible to configure somewhere the right URL
http://<srv>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<cchannel>
2) The generated WSDL is not according to the basic profile for WSDLs - wrong encoding="ISO-8859-1" - supposed to be "UTF-8"|"UTF-16" - is it possible to configure how the WSDL is generated?
I'm not sure, but I think there is a issue related to the type of binding for a binding.
3) A web service can consists of several methods - is there a tool for generating a WSDL for several interfaces?
It's "boring" to manually copy-paste from several generated WSDLs to one main WSDL for a web service
Anyway, by using XMLSpy and SoapScope, everything works just fine

a single data type will refer to multiple data types data.
You can refer one Data type in other Data Type but it wont be available under a different root node.....the root node will the the DT name under which you are referring the other DTs......you can do this by:
DT --> Give the appropriate name to a node --> While selecting the Type for this node select Data types --> select the DT from the list available....for this you should first include all the schemas in IR i.e. you should first create individual DTs by importing the schema (DT --> XSD --> Import Data Type Definition from File)
You have a huge list of schemas!
Regards,
Abhishek.

Integration Directory - Cache Notifications Error!!

Hi ,
When i try to select "Cache Notifications" in directory i am facing this error below.
<b>Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server></b>
I can see in SLD -> technical system -> exchange infrastructure, the entry for Integration Directory is missing. I ve applied note 764176 , but it is not helping. Similarly the entry for RWB is also missing here.
ve checked in SLD -> Admin -> Content Manitenance and the assocations are missing for IR & RWB. I beleive these errors are closely related. ve chked exchange profile XIDIRUSER & XIRWBUSER pwds , chked the roles , they are the same as our DEV / QA envionments.
Can anyone pls point what am i missing here
Thanks
Saravana

Hi Saravana,
About the roles for XIRWBUSER...you can check the same in the ABAP stack...go to transaction SU01 and check the Roles attached...it should have the following entries...
SAP_SLD_CONFIGURATOR
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
These should be sufficient as it is working for us...also...the roles gets passed along from the abap stack to the J2ee stack....
Now to your original issue...we had to change our sld in our system to a new box and had to re-configure....we got the same error that you were getting...
we corrected it by doing the following...
Corrected the entries in the Visual Admin under SLD data supplier service... for the HTTP tab as well as the CIM tab.
Did the SLDCHECK(TCODE on abap stack) and made sure everything was ok....
Did a CPACache refresh full...and of course a restart....
that solved the issue for us...
Thanks,
Renjith

Error while assigning Business Systems in Integration Directory

Hi,
I'm getting an error when trying to assign the business systems in the integration directory.
The error i'm getting exactly is "access to object list of type BusinessSystem using the internalEOAService BusinesSystemAccessor failed " .
I've cleared the SLD_cache and checked it but the same error.
The business systems are appearing when i tried the transaction code SLD_CHECK and is in green status.
what might be the error.

Hey
just want to make sure,are u using communication channel with party or without party.
also make sure that user has sufficient authorizations
http://help.sap.com/saphelp_nw04/helpdata/en/c4/51104159ecef23e10000000a155106/content.htm
Thanx
Ahmad
Message was edited by:
Ahmad

Value Mapping - Mass replication and Integration Directory interface

Hello all,
The following question is often approched in this forum but answer is never cleary provided. Thus I'm sorry to ask it again.
We are using Value Mapping mass data replication using special interface provided by XI. We can easily see results in cache using Cache Monitoring tool in RWB.
My question is :
Is it possible to see and then to maintain such data (mass replicated) using Integration directory (Tools > Value Mapping menu)
In this menu, we don't see our loaded data.
How to do this ?
Thanks a lot.

Hi Jean-Charles !
We also use VMR, and we find no way to access the cache data from Integration Directory. I think that by design this is not possible.
Value Mapping Replication for Mass Data
http://help.sap.com/saphelp_nw04s/helpdata/en/2a/9d2891cc976549a9ad9f81e9b8db25/frameset.htm
You cannot display the replicated value mapping data in the Integration Directory user interface (see Displaying/Editing the Value Mapping Table) since the original runtime data is stored in the application from which the data is copied. The value mappings created in this way using the user interface of the Integration Directory are just one of many possible sources of data.
Regards,
Matias.
ps: please award points if helpful

External program interfaces SLIN Error

Dear Experts,
                  I am getting SLIN External program interfaces error . could you please tell me how to correct the error ?
*LOOP AT lt_p0001 INTO ls_p0001."
      SUBMIT yhrin_rhstru00 WITH pchwegid = 'O_S_P' WITH pchobjid-low = ls_p0001-orgeh "#EC *
      WITH pchbegda = '19000101' WITH pchenda = '99991231' WITH pchplvar = '01'
      WITH pchotype = 'O' AND RETURN.
      EXIT.
    ENDLOOP.*
Regards,
Sivakumar.A

Dear experts ,
I am receiving the following SLIN Error Message.
Program: SAPLYHRIN_MSSDB_ENH Include: LYHRIN_MSSDB_ENHU06 Row:    129   (Prio 1)
PCHOBJID-LOW is not a parameter or a select option in report YHRIN_RHSTRU00
(The message can be hidden with "#EC *)
      Program: SAPLYHRIN_MSSDB_ENH Include: LYHRIN_MSSDB_ENHU06 Row:    129   (Prio 1)
PCHENDA is not a parameter or a select option in report YHRIN_RHSTRU00
(The message can be hidden with "#EC *)
Thanks and Regards,
Sivakumar.A

Labview program interface

Dear all,
I have a some problem in running my labview program.
I intention is to generate an output voltage by using my machine (by Nanonis), thus I am using their program in Nanoinis program interface. However, I might have make some connection wrongly somehow as it is not working. I want to try controlling the duration of the output voltage, maybe like 10 seconds. However, I must have made an error somewhere in the program as no voltage is generated
I would appreciate if anyone can advice me on this matter.
Thank you.
Regards,
uranus999
Attachments:
RelayOutput(Analog output) (trial).vi ‏19 KB

Dear Lynn,
I understand that it might be difficult to understand with looking at the Nanonis sub vi's. Sorry about that. If I upload a PDF of the block diagram, would it help at all?
Anyway, I should clarify one thing about the program. Actually, previously, I have use the similar block diagram but I have tried to generate the voltage by using a DAQ. This time, since I intend to use the Nanonis programming interface (replacing the wire lines) from the relay output to the programming interface-Open App ref instead of the NI daq. I expected that it should work but unfortunately, although the program work for the NI DAQ, it doesn't for the Nanonis programming interface. Thus, I am seeking advice on what might had happen and what I should do. I am still a new in writing Labview programs, thus I really do appreciate to get all the advice that I can get.
Thank you.
Regards,
uranus999

SLD Application Programming Interface for ABAP-Based Systems

Hi Experts,
Could you help me to configure the connection between SLD ABAP API and the SLD manually?
Why we use SLD Application Programming Interface for ABAP-based systems (SLD ABAP API)?
please help.
Sushama

You have to use transaction SLDAPICUST in the business system to define the SLD access data. This data consists of the host and port of the SLD as well as a user and password (PIAPPLUSER, for example). You can use the entries that you maintained on your Integration Server.
The RFC destinations LCRSAPRFC and SAPSLDAPI are used for the SLD connection. They use the SLD access data maintained with transaction SLDAPICUST. The RFC destination LCRSAPRFC is used to read the exchange profile; SAPSLDAPI is used by the ABAP API.
The RFC destinations are also used to retrieve the information about where to retrieve the information about where to find the Integration Builder required for the proxy generation. This information is located in the exchange profile.
You have to create both RFC destinations in your business system. They use the same registered server program, which is defined as part of the RFC engine settings of the J2EE Engine on the Integration Server host. This means that all business systems can use the same server program for their RFC destinations LCRSAPRFC and SAPSLDAPI. This program ID is:
● SAPSLDAPI_UNICODE for Unicode business systems
● SAPSLDAPI_NONUNICODE
This should help

To create interface using Integration Repostiory and Integration Directory

How To create interface using Integration Repostiory and Integration Directory for Java appln???

Hi,
Are u talking about Java based applications. If so, one of the way is to go with Java Proxies.
Go thru these for more:https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702
Rgds,Moorthy

Interface Mapping Not Found in Integration Directory

Hey guys!
I'am getting this error in the test configuration part of the integration directory:
"Interface Mapping: <Not Found> com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping"
I don't see why I should be getting this error since I have properly defined a message and interface mapping for the receiving interface.
BTW, I get this error when I use XSLT mapping. If I point my interface mapping to a normal message mapping, I get no error. Is there anything I am missing?
Regards,
Glenn

The weird thing is that when I test the the configuration in the Integration Directory, it is still looking for my old message mapping (the one i created using xi editor) even though I already replaced the referenced message mapping in the interface mapping to the XSL one.
Yes, I tested the interface mapping with the same data using the XSL mapping and there's no problem.
When I send the message though, I get an error saying "NO_RECEIVER_CASE_ASYNC" I really don't see why it should not recognize the receiver. I tried refreshing the cache but it still looks for my old mapping program...
:P

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

XI Error in Integration Directory adapter list is not display.

Hi All,
We are getting following error message while creating communication channels in Integration directory. More over we have attached error log file with this message.
ERROR :-
u2022     Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://xxxxx:50000/rep/query/int?container=any" with user "PIDIRUSER". Response code is 503, response message is "Service Unavailable" (HCX_COMMUNICATION_ERROR)
Apart from this if we try to refresh the xi cache with T-code SXI_CACHE it show the following error. For same I have already checked the Troubleshooting Guide for How To handle Caches in SAP XI and found every thing is ok.
ERROR :-
com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://xxxxx:50000/rep/hmi_service_swc_manager/int?container=any" with user "PIDIRUSER". Response code is 503, response message is "Service Unavailable"
     at com.sap.aii.ibdir.server.abapcache.content.CacheSwc.addContent(CacheSwc.java:63)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:360)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:324)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.setXmlDataAndBufferSize(CacheRefreshSession.java:121)
     at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.<init>(CacheRefreshSession.java:40)
     at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.getInstance(CacheRefreshSession.java:54)
     at com.sap.aii.ibdir.web.abapcache.CacheRefreshServlet.doGet(CacheRefreshServlet.java:45)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
So please guide us to solve the above mention problem.
Thanks,
Harshal

Hi...
Contact your basis team .
Regards,
Leela

Message interface not listed in integration directory

hi,
i have created 2 interfaces inside my message interface........
both are outbound.....!!
i am actually doing 2 scenario's inside the same name space......
when i go to integration directory i am no able to get one of the message interface's while creating the receiver determination and all those things.........?

if ur using business service then just
add outbound interface in receiver side and
inbound interface in sender side.
or if u r using business system then the problem is in ur SLD.
just check ur business system over their.
thanks
reward point if helpful .

No business system in integration directory error...urgent pl

Scenario: SAP800 to SAP812 via XI3.0 Using Idocs and IDoc adopter.
When I create a business system for SAP800 and SAP812 in integration Directory, it is not visble in the Integration server where I configured the Idoc adopter and thus the Idoc_inbound_asychronous is throwing a error back to SAP800" No service for business system SAP800 in integration Directory".
What may be the problem? And Pl help in Debugging the creation of business system in Integration Directory...
Thanks.

Hi,
make sure that the logical system names are properly assigened to the business systems in the Directory. To to so double click one of your Business Systems and select the menu entry "Adapterspecific Identifiers".
If the logical system name is not maintained here, make sure that it is so in the SLD (check the clients of your technical system in the SLD).
Maintain them, if necessary, clear the SLD Cache in the Directory (Menu: Environment->Clear SLD..), go to the Adapterspecific Identifiers (in edit mode) and click the second button to load the data from the SLD.
Did this fix the problem?
Regards,
Hans Christian

Using Integration Directory Programming Interface Error Wrong_Version

Similar Messages

Maybe you are looking for