Rosettanet tool testing.

Hi All,
Anybody worked on RSTK tool to test the rossettanet PIP messages need help in preparing test scripts for RSTK.....
Thanks in advance,
Srinivas.
Edited by: sri_rambo on Oct 29, 2009 6:43 AM
Edited by: sri_rambo on Oct 29, 2009 7:41 AM

/people/shabarish.vijayakumar/blog/2008/04/28/the-rosettanet-stk-and-how-to-use-it-to-your-advantage
not sure if this is what you are looking for. But does this help?

Similar Messages

Rosettanet Self Test Kit and XI

Hi,
We have developed some Rosettanet scenarios and now recently installed the Rosettanet Self Test Kit.
But we are finding it a bit confusing to link both XI and STK. How do we actually use the STK to test the scenarios with XI ?
ShaBZ ~~

I found this from one of the threads, a reply by Sam Raju;
>>>>>>
Part I. Test Using STK
In your XI ID:
1) Define both the parties 1) Shipper(Your Partner) 2) Receiver(Your company) with identifiers like DUNS Number.
2) In ID goto>Tools>Transfer Integration Scenarios from IR-->select the scenario "PIP3B2_Receiver" from the drop down list.
3) Follow the 4 steps in the config wizard.
4) While creating your CC, create it from the channel template delivered with the RosettaNet BP.
4.1) Specify the URL for STK which should be in the following format
http://<STK Server>:<port>/rosettanet/servlet/listenerServlet?userId=<Party Name> >> the server is my ip but then what is the port ? Also i am using the default user TesterA so is it the <Party Name>
4.2)In the location fields, enter your location and your partner location. >> your location and partner location -> can anybody elaborate ?
In your STK
1) Start the RosettaNet STK.
2) enter the UserID<Partner Name in XI>
3) Select the Test Scenario, 3B2V01.01-AdvanceShipmentNotification-0001-Scenario-Shipper
4) Enter Global Business ID(DUNS Number) and Location ID for both the partners. These fields should be same as in your R/3 Party configuration.
5) Enter the URL as follows:
http://<XI Server:<J2EE_Port>/MessagingSystem/receive/RNIFAdapter/RNIF
If everything is configured correctly as mentioned, you should be able to test your single-action scenario.
~~~~~~~~~~
We have developed scenarios for PIP3A4's and 3C3's in XI and need further help to test it.

How To Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
 HTTP connection to ABAP Runtime failed.
 Error: 403 Forbidden
 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
Sender
Service : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
Receiver:
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

Msi p67A gd80 - Intel processor diagnostic tool test.

Just ran the Intel processor diagnostic tool test, when I leave all settings to default i get test FAIL.
If I swith off the "Base Clock Test"I´m able to complete the test.
Is this normal?
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19792

Yes, ran the first test at 4400 mhz and mem 1866mhz.
changed these to default setting 3400 mhz and 1333 mhz, but if I leave the Base Clock test on, i get
the following.:
==================================================
--- FSB NOT Supported on this Processor ---
--- Running Base Clock test ---
Detected Base Clock --> 99
!!! --- Base Clock test Fail --- !!!
==================================================
Eventhough the Base clock in the bios is set at 100, I just see Intel Detected 99?
should if increase the base clock slightly in the bios and if so to which setting 101?
tks.

DB failed in transport tool test STMS

Hi all,
I have a problem. It looks simple but I tried to resolve it with known way without sucess.
I have two systems BWD (develop) and BWP (production).
I configured in stms domain and transport group for these systems. Auth on DIR_TRANS is set properly, variable SAPTRANSHOST is set in hosts file.
Tests in STMS of connection, transport tool and tsadm for BWD is ok. BWD is the domain controller.
When i'm testing BWP connection, tsadm are ok but transport tool return an error.
(dbms_type is not set. error code 0249.)
db is mssql.
I check env variables for user bwpadm and they disapear. I try to use ntenv2reg.exe but no variables are set.
I try to add from OS to user bwpadm all necessary variables but after restart they disapear.
Also I try to add these variables via regedit software-sap-bwp-enviroment and also after restart variables are missing.
I don't have any other idea how to do set these variables...
please help
Regards,
Michal

1. Check to see you are running the right kernel, sometimes a 32 bit kernel will actually run in a 64 bit environment, but when cycling the service the registry won't get updated.
2. Make sure you are running the latest version of the kernel.
3. Worst case, remove then add the service back in, do both with sapstartsrv.exe. When adding the service back, make sure to check the box which says use the user environment variable and put in the user running the service there.
4. The user environment variable should contain all the necessary information.

Verifier tool tests - any information or descriptions?

Hi,
I have an EJB application that has suddenly developed a mysterious problem that is preventing it from being deployed, quite a concern at this stage...
The verifier tool informs the following for each of the 4 SessionBeans being used:
Item: XxxxxxSessionEJB
Test Name: tests.ejb.elements.EjbReferencesElement
Result: FAILED
Detail: Unexpected error in verifier, check for problems related to: [ java.lang.NullPointerException ]I searched the forums and found some topics from 6-12 months ago, but nobody had any answers then.
Does anybody know where there are details on the tests performed by the verifier tool? What is the EjbReferencesElement test exactly? I guess something to do with relationships between EJBs, but what? Where can I find any information on this topic? Or how can I ignore the errors and deploy anyway?
Anything has to be better than "Unexpected error"! That is the most useless error message ever.
Any help greatly appreciated.
Ben
The full contents of Results.txt is:
                   FAILED TEST - EJB tests
Test Name: tests.ejb.elements.EjbReferencesElement
Test Assertion: References to other beans homes test
Detailed Messages:
   Unexpected error in verifier, check for problems related to: [ java.lang.NullPointerException ]
Test Name: tests.ejb.elements.EjbReferencesElement
Test Assertion: References to other beans homes test
Detailed Messages:
   Unexpected error in verifier, check for problems related to: [ java.lang.NullPointerException ]
Test Name: tests.ejb.elements.EjbReferencesElement
Test Assertion: References to other beans homes test
Detailed Messages:
   Unexpected error in verifier, check for problems related to: [ java.lang.NullPointerException ]
Test Name: tests.ejb.elements.EjbReferencesElement
Test Assertion: References to other beans homes test
Detailed Messages:
   Unexpected error in verifier, check for problems related to: [ java.lang.NullPointerException ]
                   WARNING TEST - EJB tests
There are no EJB tests tests with status of warning.

OK the problem is fixed now. Basically the deployment descriptors were incorrect.
When I upgraded from j2sdk EE 1.3 to the 1.3.1 version, the verifier tool produced much more useful output, which enabled me to correct the problem.
I would still be interested, though, if anyone has any information or links on the actual tests performed by the verifier tool and their meanings.
Ben

Are testing tool effective

Hi,
I am trying to test my scenario using 2 available method of testing. I deliberately put a wrong data and tested in message mapping.
As expected, my mapping fails in test tab of message mapping. Now i took the same payload ( whcih has wrong data) & used it in Runtime workbench ( Integration engine- Test Message) & also in ID in Tools-Test Configuration
To my surprise, the messages are triggered without error and i can see sucess flag. However when I see the XML payload it has wrong data. My Question is why these tool did not recognized what message mapping test found. How effect are those tools considering that they simulate the pipeline steps.
Regards,

When you do a mapping test, the only thing that you are testing is the mapping, independently of interfases.
When I want to test any interface, I:
1) Log on into R/3. Look for an existing IDOC in TC WE02 with status 03 (data passed to port OK). When I found one, I write the idoc number and then I go to TC WE19 and I test it there; just put the idoc number in textbox "existing idoc" and press F8, when you go to next screen, press F7 and put there the amount of Idocs that you want to reprocess. Then, log on into XI and go to TC SXI_MONITOR and see if the xml generated by the idoc you reprocess was sent ok.
2) Log on into IR and in message mapping go to test; test it putting information in the outbound idoc or xml or rfc. When the mapping result is ok, save that xml.
Then, I use a http page that basis guys give to me long time ago, where I have only to put:
Server Host (your server host, like srv-xxx-adm for example)
Server Port (in this case, I test it with server 8000 and not 50000)
Client (your mdt in SAP R3)
Quality of Service (sync., async. or exactly once in order)
Sender Service (your sender service; you can found it in ID)
Sender Interface (your message interface in IR)
Sender Namespace (your namespace in IR)
Then, you can upload the xml and logon with a username and password, and the xml will be sent.
And like in 1), you must log on into XI and go to TC SXI_MONITOR and see if the xml generated by the idoc you reprocess was sent ok.
3) Some guys from other systems are using a program called xmlspy to send xml from any system throw xi to sap or from sap throw xi to any system. The only thing that I have to do is to send them the empty xml I got from message mapping in IR, so they can fill it with information and send it. Then, just look at it in sxi_monitor transaction code in xi.
I dont use the other test tools because last guy in xi here told me not to use it (he didnt explain me why).
I hope this could be helpful for you.

Unit Testing

Hi All,
I would like to inform to all, can any one explain to me the concept of Unit testing in FICO and how it should be drawn? If possible send any dcoumentation for this focus to my mail id: [email protected]
Thanks with regards,
Bala

Hi
refer below reward if helps
Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
Security testing you will be testing different roles and functionalities and will check and signoff.
Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.
Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.
User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
We use different software during testing. Most commonly use are
Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.
Mercury Load Runner: is used for performance testing. This is an automatic tool.
What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?
Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed.
Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
What kind of testings that are carried out in testing server?
1. Individual Testing ( Individually which we've created)
2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)
The 3 types of testing is as follows:-
1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
2. Integration testing (where a process is tested that cuts across all areas of SAP).
3. Stress testing (where lots of transactions are run to see if the system can handle the data)
http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm
Unit test issues
The unit tools test all SAP development work that handles business object processing for the connector. Also, the unit test tools enable you to test the interaction of your work with the ABAP components of the connector. The test tools allow you to test your development work as an online user (real-time) only.
Note:
It is important to understand the differences between testing the connector as an online user and testing the connector as if operating as a background user.
The differences between testing the connector as an online user or as a background user are described as follows:
Memory--When testing a business object, the connector must log into the SAP application.
      The connector runs as a background user, so it processes in a single memory space that is never implicitly refreshed until the connector is stopped and then restarted (therefore it is critical in business object development to clear memory after processing is complete). Since you are an online user, memory is typically refreshed after each transaction you execute.
      For more information, see Developing business objects for the ABAP Extension Module. Any problems that may occur because of this (for example, return codes never being initialized) are not detected using the test tool; only testing with the connector will reveal these issues.
Screen flow behavior--Screen flow behavior is relevant only when using the Call Transaction API. The precise screen and sequence of screens that a user interacts with is usually determined at runtime by the transaction's code. For example, if a user chooses to extend a material master record to include a sales view by checking the Sales view check box, SAP queries the user for the specific Sales Organization information by presenting an additional input field. In this way, the transaction source code at runtime determines the specific screen and its requirements based on the data input by the user. While the test tool does handle this type of test scenario, there is a related scenario that the test tool cannot handle.
      SAP's transaction code may present different screens to online users versus background users (usually for usability versus performance). The test tool only operates as an online user. The connector only operates as a background user. Despite this difference, unit testing should get through most of the testing situations.

My graphic card failed but passes the recall test - surely Apple would replace it? How wrong can you be!

Even though I had read about the product recall on some iMacs, mine had never had an issue, but to be safe, the plan was to take it to an Apple store to have them test and replace it.
A week ago, on occasion, the screen suddenly started going completely gray, everything else seemed to be working fine, and any apps running would continue to do so. Without being able to see the screen, the only options was to power it down, run any diagnostic test and start normally. It passed pro tools tests, with no warnings so I thought it could have been a software issue. After many restarts without anything else plugged in, the iMac appeared to function for maybe a day or so, but gray screen whenever it wanted to.
So I called Apple, they told me to get it into a service centre, and they would do further tests. Whilst on the phone to the engineer, my iMac with the gray screen suddenly refused to power back up. The engineers tell me that the graphic card fails any benchmarking tests with corruption and the same gray screen issue, so it looks promising yes? No. The specific tests that the machine must fail for the recall - passed.
Having spent almost an hour on the phone to a Apple senior advisor today, he tells me that it is not covered by the recall !!
The machine is one of the matching serial numbered machines in the recall, it has suddenly developed a graphic card issue that leaves the machine unusable, it suddenly started having this problem within weeks of the recall being announced - It has the faulty card in it, it has the fault - yet it does not qualify?
Can someone please tell me what I could have done to get this card replaced without the estimated £250 charge to get my machine running again.
I am a die hard Apple enthusiast, I have converted everyone I have been in contact with to purchase from them for their legendary customer services and yet feel perplexed as to what I should do next.
My first reaction is to raise a big fuss about the situation at an Apple store, but I can't blame them too much if my machine does not match the recall criteria - but come on, it can't be a coincident that this card has failed now, can it?
What do I do next. I don't want to take my machine over to proper Apple store and raise a fuss, that would be counter productive. But really Apple
Anyone have a suggestion - would you buy another iMac that could have the same problem and get the same response?
To any Apple engineers out there who can look at a case number my ref number is 500592345, apparently there is a lot of info in there, but nothing that will help me!

Apple engineers do not participate here. The only replies you will normally get are from people who are, like me, just fellow users, and there's nothing any of us can do to intervene in this matter.
If Apple says that your system is not covered by the recall, there's not much you can do. You can try taking your system to an Apple Store and politely - do not "make a fuss"; polite but gently insistent is much more likely to get you useful results - ask for assistance. Or you can call Apple tech support, ask to speak with customer relations, and explain the situation to them and request coverage under the recall program.
If all that fails, though, then you're probably at a dead end and will need to pay for the service if you want it done.
Regards.

XI Debugging tool in the Configuration -Integration Builder

Hello to XI Experts,
I an testing the XI Debugging tool in the Configuration -Integration Builder
Menu Path is : Tool->Test Configuration.
It is simple Idoc to Flat File Mapping and it gets executed .
However when I test it using the Test Configuration I am getting following error below.
Internal Error
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://dellsaperp:8050/sap/xi/simulation?sap-client=100 User: XIDIRUSER
There is no problem with mapping as it is getting executed .I am unable to make the Test Configuration work. Do we need to do any configuration to make this transaction work? Any clue?
Regards,
Prashanta Ghosh

Hi Prashanta -
In TC SICF, make sure the simulation service is activated. Path should be default_host/sap/xi/simulation. If not, right-click on simulation and activate service.
Regards,
Jin

Test FCC without triggering scenario, similar to "Test Configuration" in ID

Hi,
lets say, we are using FCC in receiver file adapter, is there any way to test the FCC conversion (without actually triggering the scenario).
in ID, i see there is a nice tool "Test Configuration", but it ends at ReceiverAgreement and shows the Outgoing message as XML,
is there any way go a step further to see actually the fcc output, or any alternative way.

is there any way go a step further to see actually the fcc output, or any alternative way.
no alternative way to test the Scenario and only possiable with run time .
Test Configuraion : name it self only possiable to test Configuration only.......correctly configured /not..

Integrated configuration (PI 7.1) throws error when do 'Test Configuration'

I am doing Proxy to Web Service (SOAP) sync scenario. We are using Integrated Configuration. After created integrated configuration and test this from (Tools --> Test Configuration) it throws the following error at the receiver agreement step.
Sender Agreement - Green
Receiver Determination - Green
Interface Determination - Green
Operation Mapping - Green
Receiver Agreement - Red.
Problem occurred in receiver agreement for sender -DR4400_D to receiver -ESRI,urn:AssetManagement.AddressManagementSearchCapabilitiesFromECC_Out: No standard agreement found for , DR4400_D, , ESRI, urn::AssetManagement, AddressManagementSearchCapabilitiesFromECC_Out

Test Configuration cannot be used to test Integrated Configuration Scenario.....refer my reply here:
Re: Integrated Configuration in PI7.1
Regards,
Abhishek.

Removing pulldown... cinema tools vs compressor vs ???

I have some footage shot at 24p on my canon hf 10. I need to remove pulldown. I saw this artice here
http://support.apple.com/kb/HT2410?viewlocale=en_US):
now, which is a better method, to remove the pulldown, cinema tools or compressor, or even, another third party app does it better? Compressor and Cinema tools are 2 different programs, so they must have 2 different ways of doing things, and or results.
with compressor I have created a setting and a droplet on my desktop.
but I am interested in what the article says
*This method requires that you determine the cadence pattern for each clip.*
*In Final Cut Pro, choose the Easy Setup named "Apple Intermediate Codec, 29.97, HDV-Apple Intermediate Codec 1080i60".*
*Capture your clips.*
*Open each clip in Cinema Tools and manually reverse telecine each clip.*
how do I determine the Candence for EACH CLIP? also, if I shoot at 30p, do I also need to remove pulldown, or is this just for 24p?

piff aroni wrote:
I have some footage shot at 24p on my canon hf 10. I need to remove pulldown. I saw this artice here
http://support.apple.com/kb/HT2410?viewlocale=en_US
Zak Ray wrote:
Not sure why the article is recommending using AIC-- as I see it, your options are 1) capture native HDV and transcode to ProRes + reverse telecine in Compressor, or 2) capture ProRes and reverse telecine in Cinema Tools.
The best way to figure it out is probably to just run a test.
Am in a very similar situation to Piff, and as Zak suggests am about to do some tests.
Meantime though, would be interested to hear from anyone with experience in this particular area, especially since the Knowledge Base article quoted above is a bit confusing on two fronts:
1) It refers to the Canon HV20, which shoots HDV, whereas the camera referenced by the original poster, the Canon HF10 -- assuming it's the same Canon HF10 I've been using -- shoots AVCHD files on SDHC cards (and/or its internal memory);
2) As Zak points out, it's surprising that there's no mention of ProRes, just AIC. The article says it was last modified July, 2008 -- was that pre-ProRes?
In any case, I'll try to post my results as soon as I can run my own Compressor vs. Cinema Tools tests -- but in the meantime would appreciate hearing any insights from those who've already been down that road, especially in regards to best practices for removing the pulldown added by the Canon HF10 when shooting "24p" (which as a colleague recently pointed out, should actually be called "24f", as in "24fake" -- since it's really just 29.97 interlaced in disguise).
Thanks,
John Bertram
Toronto

How to test integrated configuration?

Hi,
I've set up an Integrated Configuration.(ICO)
I know i cannot test from Tools >> Test Configuration
I'm testing from RWB, i suppose i have to put my xml using the adapter engine test message option instead of the integration engine test option. You think that is correct?
Whatever i do i still get an error message saying there is no receiver determination for the given business component and interface. I thought for ICO you dont need Receiver Determination? Am i wrong?
Are there other/better ways to test this ICO?
Thx
Robert

Hi,
Small recap of the issue: i want to test an Integrated Configuration from the RWB.
My scenario is File to SOAP (synchronous)
All cache refreshes both in SXI_Cache and CPA cache were good.
If i test from RWB >> INtegration Engine >> Test Message then i get the following return:
".... Error While Sending Message: Error stack from response: No receiver could be determined...."
(this response is understandable: ICO is not on the IE and the combination of Sender Component/INterface/Namespace will not be found there, so we get an error)
But...
If I test from RWB >> Adapter Engine >> Test Message with these details:
Sender Component = Sender Comm Component from ICO
Interface = Sender Interface from ICO
Namespace = Sender Namespace from ICO
User/Passw are good
QoS: Best Effort
XML = good
then i get the following result:
"....Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=TEST_ICO;TS=;AN=SIOS_ICO_ReadCustomer;ANS=urn:vitens:isu:installation:create; in the current context [Unknown]. ......"
receiver agreement?
So i wonder if it is possible at all to test the ICO from the RWB?
Any comments are helpful.
Also i'm wondering if there could be installation settings wrong for AAE (we're on PI 7.11)
Or maybe there are settings in the Service Interface i should do differently?
Kr
Robert

Error occured during the "test of the interface"

Hi,everybody
where I do the "Test Configuration" in the ID(Tools->Test Configuration),an error occured.
Internal Error
 HTTP connection to ABAP Runtime failed.
 Error:403ForbiddenURL:http://NEUESDNWXI01:8001/sap/xi/simulation?sap-client=500
 User: PIDIRUSER
what can i do with the error?
Thanks

Hi
Check if the service for testing in XI (in transaction SCIF)is turned on,
Note :Forebidden is generally an auth or password error. 
Also Check This
4) Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
Because of Inactive Services in ICF Go to SICF transaction and activate the services. Refer SAP Note -517484
Error in RWB/Message Monitoring- because of J2EE roles Refer SAP Note -796726
Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. Because of the URL is incorrect or the adapter is not correctly deployed.
Regards
krishna

Rosettanet tool testing.

Similar Messages

Maybe you are looking for