SAP Portal server node identifier

Hi:
We have SAP Portals installed in two server nodes with a load balancer.
I know SAP gives a unique internal identifier (number) by server.
I want to know, where can I find this identifier ?
Thanks,
Felipe Mendivil Ortiz

Open the Visual Administrator - it will show you the server and dispatcher processes with their identifier.

Similar Messages

Deactivate Portal server node from Web dispatcher, but still keep online

We want to deactivate a Portal server node from the Web dispatcher. We also need to connect directly to the specific node.
We configured the Server Node using Config Tool --> Server_ID####### --> Debug --> Debuggable --> Restricted Load Balancing. The node is not available to the Web dispatcher, However we are unable to explicitly connect to that node. We get the error message in the browser:
503 Service Unavailable
SAP WebAS engine is starting...
If this state does not change within a few minutes,
please contact your system administrator.
Check the recommendations in SAP Notes: 943498, 764417
Message: Dispatcher running but no server connected!
I have also read through the Web dispatcher online Help. They mention creating groups but they all seem to pertain to ABAP groups using SMLG. Our Web dispatcher is used in a strictly J2EE environment.
There must be a Profile setting or some config to restrict specified nodes... Let me know if you have found out?
Thank You,
Jon Sells

Hi PR,
Yes I understand that the Web Dispatchers Job ends at that point. That's why I want to stop the requests at the Web dispatcher by not allowing those nodes to be available.
Here is the situation. We have 3 Windows Servers with 10 Server Nodes spread accros them.
Host A - 2 Server Nodes, Central instance (Message Server) and SQL Server DB.
Host B - 4 Server Nodes.
Host C - 4 Server Nodes.
The Going Live Analysis suggested we move the DB off of the CI. We cannot do that at this time. What we can do is shut down the 2 nodes on Host A. Instead of shutting them down, we would rather remove them from the WD group. that way, our users never connect to the 2 nodes on the CI but Basis can still use them for Administration and those 2 nodes on the CI are never used for production purposes. Those nodes will just be used for monitoring and maintenance or even emergency purposes.
Right now our process to remove the 2 nodes from the Web dispatcher is to connect to the Admin page for Web Dispatcher --> Monitor Server Groups --> Right Click on the Host and select Deactivate. We have to do this whenever the Message Server is retarted. The million dollar question: How can that be set via a startup parameter?
Thanks
Jon Sells
Here is an example of how you can connect to a specific node:
https://<Host_name>.domain.local/b2b/b2b/init.do;sapj2ee_irj=7501753

Enterprise Portal server node monitoring

Hi all,
I have an Enterprise Portal system based on SAP NW 7.02. I have 3 server nodes with max heap set to 3GB (I just created the 3rd server node).
I have a few questions regarding the monitoring part.
1) When a request comes from users, the dispatcher will send the request to the server node based on the load on the server nodes. Am I right?
2) Is there some way (tool or logs) I can measure the load on each server node at any point in time?
3) How do we interpret the content of the file dev_server0:
(a) Mon Apr 28 11:10:42 2014
48826.084: [GC 48826.085: [ParNew: 474420K->58192K(512000K), 0.1508051 secs] 1009031K->594433K(3043328K), 0.1513562 secs] [Times: user=0.80 sys=0.03, real=0.15 secs]
For example, 474420K was cleared to 58192K, what is 512000K? What are the remaining values?
(b)
Thu Oct 24 17:40:32 2013
68937.562: [CMS-concurrent-mark-start]
68937.572: [Full GC 68937.572: [CMS
Thu Oct 24 17:40:39 2013
68944.836: [CMS-concurrent-mark: 7.253/7.273 secs] [Times: user=7.29 sys=0.03, real=7.27 secs]
(concurrent mode failure)
This one is an earlier one when I had 2 nodes. Please help me interpret this also.
regards.

Hi all,
Thanks for the clarification.
I'll close the message now but just one last thing:
Even after adding the 3rd node, I got the full GCs and had to restart the system a few times:
Wed May 7 10:40:04 2014
47339.492: [CMS-concurrent-preclean: 0.680/1.488 secs] [Times: user=1.68 sys=1.36, real=1.49 secs]
47339.493: [CMS-concurrent-abortable-preclean-start]
47339.493: [CMS-concurrent-abortable-preclean: 0.000/0.000 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
47339.496: [GC[YG occupancy: 410037 K (512000 K)]47339.497: [Rescan (parallel) , 0.5012912 secs]47339.998: [weak refs processing, 0.0048337 secs]47340.003:
[class unloading
Wed May 7 10:40:05 2014
, 0.1856070 secs]47340.190: [scrub symbol table, 0.4474248 secs]47340.637: [scrub string table, 0.0371698 secs] [1 CMS-remark: 2478114K(2531328K)] 2888152K
(3043328K), 1.3325627 secs] [Times: user=10.39 sys=0.23, real=1.33 secs]
47340.830: [CMS-concurrent-sweep-start]
Wed May 7 10:40:15 2014
47350.605: [Full GC 47350.606: [CMS47350.940: [CMS-concurrent-sweep: 5.122/10.110 secs] [Times: user=12.70 sys=8.57, real=10.11 secs]
(concurrent mode failure)
Wed May 7 10:40:35 2014
: 2531065K->2392788K(2531328K), 20.2064808 secs] 2941102K->2687033K(3043328K), [CMS Perm : 292034K->291935K(786432K)], 20.2073316 secs] [Times: user=20.22
sys=0.04, real=20.21 secs]
47370.825: [GC47370.826: [GC 47370.827: [ParNew
Wed May 7 10:40:36 2014
(promotion failed): 297544K->297773K(512000K), 0.4042734 secs] 2690332K->2690567K(3043328K), 0.4049733 secs] [Times: user=7.29 sys=0.04, real=0.41 secs]
[1 CMS-initial-mark: 2392793K(2531328K)] 2690567K(3043328K), 0.7135858 secs] [Times: user=7.60 sys=0.04, real=0.71 secs]
47371.541: [CMS-concurrent-mark-start]
How do we interpret the above? Is there some parameter that I need to further fine-tune?
regards

Improve Portal performance with BI-Java by adding additional server node.

Hi SAP Expert
I wonder anyone might have attempted this before,
In an environment with BI-Java and Portal Java stack installed on the same server, is it possible to improve the system performance by adding additional portal server node? or is there any improvement seen by adding the extra server node?
I am after suggestion and experience on how the portal performance can be improve, with consideration of BI-Java sharing Portal resources.
Any comment will be most appreciated.

Hi Jim,
We've this configuration at our site, Portal and BI running together (not federated). Recommendations would be to:
1. Set a sensibly large max heap size on each server node of Portal (at least 2GB if not larger) and implement several nodes at least. For example we have 4 x physical nodes, each running 3 server nodes of 2GB max heap size apiece so a total of 12 nodes.
2. Implement the BI Safety Belt for large results sets (1127156)
3. Implement the latest JVM / JDK you can on your environment. We found much improved performance after implementing JDK SR10 with the J9/2.3 options enabled e.g., -Xjvm:j9vm23
-Xsoftrefthreshold0
4. Patch your BI components on the Portal (BIBASES, BIWEBAPP etc) to the latest available patch level for your Portal SP level
5. Make sure all your RFC connections are load balanced to the backend and tuned for the kind of load you expect on your reports, and the BI is sized appropriately in terms of app servers and dialog work processes, RFC-enabled login groups in SMLG etc.
6. Consult notes 1048691 (especially useful, opions &PROFILING=X&TRACE=X added to reports for example for performance tracing), 937697, 1021921, 948158 for information about problem analysis for this scenario
7. Implement SAP Web Dispatcher for Portal to reduce load on static mime files
8. Tune the Portal application. There's plenty information on SDN related to Portal performance tuning.
I hope this helps!
Cheers,
Marc

Multi SAP ECC Server Connection to Single SAP Portal

Dear Experts,
We have connected multiple SAP Client of same ECC server to Single SAP Portal and we are able to view data using various standard SAP ESS/MSS Objects.
Is it feasible to connect Multiple SAP ECC Servers to one SAP Portal Server for showing data from varios servers using Standard ESS/MSS Objects.
Any help appreciated.
Rgds
Gulshan

Hi Gulshan,
You are right....these are the JCO names being picked up by standard ESS/MSS applications.
The Standar DCs will be calling these JCO names only while connecting to the SAP Server.
As you described,
The portal do have system alias name as unique name.
You may need to use some customizations.....plz find the below threads...they may be of your help.
[Thread1 - Change the JCO name (RFC_META_DATA) |Change the JCO name (RFC_META_DATA);
[Thread2 - How to change the JCO reference to an existing model|How to change the JCO reference to an existing model;
Good Luck!!!
Biroj Patro.

BlackBerry Browser Channel Push from SAP Portal

I have posted the following on blackberry forums, not much success, maybe some portal person can suggest how to move forward. I've taken some standard blackberry java code that pushes a web page to a blackberry device, and executed from my java vm and it works. I then put the same java code inside an AbstractPortalComponent, and executed from portal, it does not work. Read following posting on blackberry forums ...
I am attempting to implement a simple Browser Channel Push from within SAP Portal server.
I have successfully executed standard code from my local Java VM. I get the custom icon on my blackberry device, and when I click on it, it loads the web page from device cache.
I have moved the exact same code into a SAP wrapper method and executed from SAP Portal. There are no additions in my code relating to the push.
I get the custom icon on my blackberry, but when I click on it, a http request is performed every time.
Below is the MDS log for the successful push, from local java:
<2008-05-12 13:17:38.427 EST>:[408]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = PushServlet: POST request from [UNKNOWN @ 10.17.224.154] to [DESTINATION=Moris.T.Mihailidis @bhpbilliton.com&PORT=7874&REQUESTURI=/] : 1 bytes...>
<2008-05-12 13:17:38.427 EST>:[409]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = submitting push message with id:312ce7cb:119db0ce9da:-7fff-1036777698>
<2008-05-12 13:17:38.427 EST>:[410]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Executing push submit command for pushID:312ce7cb:119db0ce9da:-7fff-1036777698>
<2008-05-12 13:17:38.427 EST>:[412]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Pushing message to: 252597d5>
<2008-05-12 13:17:38.427 EST>:[413]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Number of active push connections:1>
<2008-05-12 13:17:38.427 EST>:[414]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = added server-initiated connection = -2031026175, push id = 312ce7cb:119db0ce9da:-7fff-1036777698>
<2008-05-12 13:17:38.427 EST>:[415]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Available threads in DefaultJobPool = 199 running JobRunner: DefaultJobRunner-197>
<2008-05-12 13:17:38.427 EST>:[416]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION =>
<2008-05-12 13:17:38.427 EST>:[416]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = [Transmission Line Section]:>
<2008-05-12 13:17:38.427 EST>:[416]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = POST / HTTP/1.1>
<2008-05-12 13:17:38.427 EST>:[416]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = [Headers Section]: 13 headers>
<2008-05-12 13:17:38.427 EST>:[416]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = [Parameters Section]: 3 parameters>
<2008-05-12 13:17:38.427 EST>:[417]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION =>
<2008-05-12 13:17:38.427 EST>:[417]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = [Transmission Line Section]:>
<2008-05-12 13:17:38.427 EST>:[417]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = POST / HTTP/1.1>
<2008-05-12 13:17:38.427 EST>:[417]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = [Headers Section]: 13 headers>
<2008-05-12 13:17:38.427 EST>:[417]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026175, HTTPTRANSMISSION = [Parameters Section]: 3 parameters>
<2008-05-12 13:17:38.427 EST>:[418]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Finished JobRunner: DefaultJobRunner-197, available threads in DefaultJobPool = 200, time spent = 0ms>
<2008-05-12 13:17:38.458 EST>:[421]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = CreatedSendingQueue, DEVICEPIN = 252597d5, USERID = u4>
<2008-05-12 13:17:38.458 EST>:[424]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = Sending, TAG = 444006409, DEVICEPIN = 252597d5, USERID = u4, VERSION = 16, CONNECTIONID = -2031026175, SEQUENCE = 0, TYPE = NOTIFY-REQUEST, CONNECTIONHANDLER = http, PROTOCOL = TCP, PARAMETERS = [CORMEL-BES03/10.16.60.49:7874], SIZE = 666>
<2008-05-12 13:17:38.458 EST>:[425]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Number of active push connections:0>
<2008-05-12 13:17:38.458 EST>:[426]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = GME, EVENT = Received_from_above, DESTINATION = 252597d5, GMETAG = 444006409, CONTENT = IPPP, CONFIRM = FALSE, SIZE = 713>
<2008-05-12 13:17:38.458 EST>:[427]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = GME, EVENT = Sent_down, DESTINATION = 252597d5, GMETAG = 444006409, SIZE = 745, SOURCE = , GUID = null>
<2008-05-12 13:17:38.458 EST>:[428]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SRP, SRPID = S82672876, EVENT = Sending, VERSION = 1, COMMAND = SEND, TAG = 444006409, SIZE = 858>
<2008-05-12 13:17:40.614 EST>:[429]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SRP, SRPID = S82672876, EVENT = Receiving, VERSION = 1, COMMAND = STATUS, TAG = 444006409, SIZE = 10, STATE = DELIVERED>
<2008-05-12 13:17:40.614 EST>:[430]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = GME, EVENT = Notification, NOTIFICATION_TYPE = DELIVERED, GMETAG = 444006409, CONTENT = IPPP>
<2008-05-12 13:17:40.614 EST>:[431]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = Notification, TAG = 444006409, STATE = DELIVERED>
<2008-05-12 13:17:40.614 EST>:[435]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Device connections: AVG latency (msecs)2156>
<2008-05-12 13:17:40.614 EST>:[436]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, Removed push connection:-2031026175>
<2008-05-12 13:17:45.239 EST>:[437]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = RemovedSendingQueue, DEVICEPIN = 252597d5, USERID = u4>
Below is the MDS log for the unsuccessful push, from SAP Portal:
<2008-05-12 13:22:20.685 EST>:[453]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = PushServlet: POST request from [UNKNOWN @ 10.17.224.154] to [DESTINATION=Moris.T.Mihailidis @bhpbilliton.com&PORT=7874&REQUESTURI=/] : 1 bytes...>
<2008-05-12 13:22:20.685 EST>:[454]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = submitting push message with id:312ce7cb:119db0ce9da:-7ffe-1036777698>
<2008-05-12 13:22:20.685 EST>:[455]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Executing push submit command for pushID:312ce7cb:119db0ce9da:-7ffe-1036777698>
<2008-05-12 13:22:20.685 EST>:[457]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Pushing message to: 252597d5>
<2008-05-12 13:22:20.685 EST>:[458]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Number of active push connections:1>
<2008-05-12 13:22:20.685 EST>:[459]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = added server-initiated connection = -2031026174, push id = 312ce7cb:119db0ce9da:-7ffe-1036777698>
<2008-05-12 13:22:20.685 EST>:[460]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Available threads in DefaultJobPool = 199 running JobRunner: DefaultJobRunner-196>
<2008-05-12 13:22:20.685 EST>:[461]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION =>
<2008-05-12 13:22:20.685 EST>:[461]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = [Transmission Line Section]:>
<2008-05-12 13:22:20.685 EST>:[461]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = POST / HTTP/1.1>
<2008-05-12 13:22:20.685 EST>:[461]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = [Headers Section]: 15 headers>
<2008-05-12 13:22:20.685 EST>:[461]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = ReceivedFromServer, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = [Parameters Section]: 3 parameters>
<2008-05-12 13:22:20.685 EST>:[462]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION =>
<2008-05-12 13:22:20.685 EST>:[462]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = [Transmission Line Section]:>
<2008-05-12 13:22:20.685 EST>:[462]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = POST / HTTP/1.1>
<2008-05-12 13:22:20.685 EST>:[462]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = [Headers Section]: 15 headers>
<2008-05-12 13:22:20.685 EST>:[462]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, HANDLER = HTTP, EVENT = SentToDevice, DEVICEPIN = 252597d5, USERID = u4, CONNECTIONID = -2031026174, HTTPTRANSMISSION = [Parameters Section]: 3 parameters>
<2008-05-12 13:22:20.685 EST>:[463]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Finished JobRunner: DefaultJobRunner-196, available threads in DefaultJobPool = 200, time spent = 0ms>
<2008-05-12 13:22:20.716 EST>:[466]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = CreatedSendingQueue, DEVICEPIN = 252597d5, USERID = u4>
<2008-05-12 13:22:20.716 EST>:[469]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = Sending, TAG = 444006411, DEVICEPIN = 252597d5, USERID = u4, VERSION = 16, CONNECTIONID = -2031026174, SEQUENCE = 0, TYPE = NOTIFY-REQUEST, CONNECTIONHANDLER = http, PROTOCOL = TCP, PARAMETERS = [CORMEL-BES03/10.16.60.49:7874], SIZE = 707>
<2008-05-12 13:22:20.716 EST>:[470]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Number of active push connections:0>
<2008-05-12 13:22:20.716 EST>:[471]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = GME, EVENT = Received_from_above, DESTINATION = 252597d5, GMETAG = 444006411, CONTENT = IPPP, CONFIRM = FALSE, SIZE = 754>
<2008-05-12 13:22:20.716 EST>:[472]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = GME, EVENT = Sent_down, DESTINATION = 252597d5, GMETAG = 444006411, SIZE = 786, SOURCE = , GUID = null>
<2008-05-12 13:22:20.716 EST>:[473]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SRP, SRPID = S82672876, EVENT = Sending, VERSION = 1, COMMAND = SEND, TAG = 444006411, SIZE = 890>
<2008-05-12 13:22:22.951 EST>:[474]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SRP, SRPID = S82672876, EVENT = Receiving, VERSION = 1, COMMAND = STATUS, TAG = 444006411, SIZE = 10, STATE = DELIVERED>
<2008-05-12 13:22:22.951 EST>:[475]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = GME, EVENT = Notification, NOTIFICATION_TYPE = DELIVERED, GMETAG = 444006411, CONTENT = IPPP>
<2008-05-12 13:22:22.951 EST>:[476]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = Notification, TAG = 444006411, STATE = DELIVERED>
<2008-05-12 13:22:22.966 EST>:[480]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Device connections: AVG latency (msecs)2250>
<2008-05-12 13:22:22.966 EST>:[481]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, Removed push connection:-2031026174>
<2008-05-12 13:22:26.138 EST>:[482]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Statistics save task started>
<2008-05-12 13:22:26.138 EST>:[483]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = SCM, EVENT = Statistics save task finished -- number of rows inserted:5>
<2008-05-12 13:22:27.248 EST>:[484]:<MDS-CS_CORMEL-BES03_MDS-CS_1>:<DEBUG>:<LAYER = IPPP, EVENT = RemovedSendingQueue, DEVICEPIN = 252597d5, USERID = u4>
The differences I see:
1) The push from SAP has 15 headers compared to 13
2) The Sending and Receiving SIZE values
Can you assist me with identifying why these differences are occurring.
If I can solve these, I believe my Push from SAP will work.

hi
You can use UME API and do a force login, but I would recommend to use this only if the user is an authenticated user.
request.setAttribute(ILoginConstants.LOGON_UID_ALIAS, "userID");
UMFactory.getLogonAuthenticator().logon(request,response,"uidpwdlogon");
you can also do a force logon using
UMFactory.getAuthenticator().forceLoggedInUser(request, response);
regards
Jagdeshwar

Create SSO on SAP portal to ECC 6.0 EHP4 backend

Hello,
I want to create a SSO connection form my SAP Portal server to my ECC 6.0 EHP4 Backend system.
My JAVA Portal is installed on the same system as the ECC 6.0 backend system.
For the configuration I follow the steps as described in the document: http://www.sap-img.com/basis/configure-the-sso-single-sign-on-for-portal.htm.
At point 5.3 I have to set the Backend System as "ACL" in the Portal. So Iu2019m still in the Visual administrator from point 5.2 but now I go to the path Server --> Services --> Security Provider --> Ticket.
Here I choose the authentication tab and want to add the com.sap.security.core.server.jass.EvaluateTicketLoginModule. Buth when I press the Add button I get a list of available login members. In this list there is no com.sap.security.core.server.jass.EvaluateTicketLoginModule login module available. Does someone know what Iu2019m doing wrong or how I could add the correct login module?
I attach a screen shot from Visual administrator.
Kind regards,
Richard Meijn
Edited by: Richard Meijn on Aug 10, 2011 8:20 AM

Cahtal,
Thanks for you quick reaction but it's not all clear for me. So could you explain it a little bit more detailed fo me.
If I write something wrong please correct me. I understand the following
So If I am on the "Authentication" tab I press the Add new button
In the list which shows up I select the u201CEvaluateTicketLoginModuleu201D
Here I change the name and option value to trustedsys01=<PORTAL_SID>, <PORTAL_CLIENT>
Kind regards,
Richard Meijn

SAP Note #723909 Clarification needed: 2G heap for server nodes

We mare upgrading from Enterprise 4.7 to ERP 6.0 SP12. For our ESS/MSS we will use standalone Java NW 7.0 SP14 with XSS SP12. Our portal servers and ERP ABAP are Unix Solaris 9 or 10 64-bit. The portal servers are 4CPU x 16G. We use three server nodes on our central instance and three server nodes on our dialog instance. All server nodes have 2G heap.
Recent load tests indicate we are reaching memory limits in the server nodes. THis causes frequent full GC with tenured objects deleted (very time consuming). We want to increase heap size > 2GB. Note 723909 seems to say this can be done for 64-bit systems, but SAP appears to recommend additional server nodes with 2G heap. I think this is because of GC performance with large heap.
- Are we supported with heap > 2G?
- Are there still concerns with GC when heap > 2G?
- Are there other reasons why heap should be no higher than 2G?
Thanks in advance

- Are we supported with heap > 2G?
- Are there still concerns with GC when heap > 2G?
- Are there other reasons why heap should be no higher than 2G?
You´ve answered your questions yourself
To have a fast J2EE engine you need to absolutely make sure all the heap is covered in physical memory. No swapping should take place at all. Once the system starts swapping in and out, you will loose a lot of performance.
How big is your Oracle SGA? If you can decrase it so all the heaps (+ dispatcher heap) will fit in physical memory you can increase more. We use 2.5 - 3 GB heap (for BI) with three server nodes.
Markus

Connecting specific server node from portal

Hello,
I am trying to access specific server node with URL "http://<Server>:<Port Number>/irj/portal;sapj2ee_irj=<Node ID>"
I am able to access portal page through the above URL, but even while entering incorrect Node ID, portal page is accessible which should not happen ideally.
I am trying to configure an alerting mechanism so that I can know which server node is up and whiich one is down when users try accessing portal.
Please provide me steps to access server node through portal and also if there is some specific portal parameter which controls the above mentioned anomaly.
Regards,
Anuradha

Hi Anuradha,
Please use something like:
http://<Server>:<Port Number>/irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default;sapj2ee_*=<NodeID>.
You can use
java_scriptj<colon>alertOpenparentesisdocument<dot>cookiecloseparentesis
to find out if you connected to the proper node. Note the sapj2ee_* parameter is optional so if the value provided is not correct it will connect you to one of the available nodes. Remove the underscore from java_script.
Replace:
java_script with javascript
<colon> with :
Openparentesis with (
Closeparentesis with )
SCN would not let me post the symbols
Best regards,
Duncan
Edited by: Duncan Speidel on Nov 22, 2011 11:20 PM

Possible to Directly Address Individual Server Node in Portal URL?

Hello,
A portal, java only, application server can have multiple JVM server nodes. The first node installed is server0, addtional nodes can follow like server1, server2, etc as needed and capacity allows. The typical URL for addressing a portal installation is http://<hostname>:<portnumber>/irj/portal. Does anyone know of a way to directly send a request to a specific node of the app server, ie. http://<hostname>:<portnumber>/server1/irj/portal?
The need typically arises during troubleshooting.
Kind Regards, Mitch

Thanks for taking the time to reply, but the information is not what I'm looking for. A distinction should be made between <hostname> and <servernode>. When I use the term <hostname> I'm talking the physical server device. When I use the term <servernode> I'm talking Java server nodes, logical units added to the SAP runtime environment to add processing capability.
In OSS 723909 you can see a recommendation, 'We recommend using additional server nodes instead of huge heaps'. It is these additional server nodes that I'm referring to in my query. You can add these additional java server nodes in 'configtool' with the menu path 'server - add server', provided the physical device <hostname> has adequate memory to support the additional node. So, configtool in a multi-host, multi-java-server node environment looks like this:
Global server configuation
instance_ID12345
     dispatcher_ID12345...
     server_ID12567
     server_ID12678
instance_ID#####
     dispatcher_ID#####
     server_ID#####
     server_ID#####
instance_ID#####
     dispatcher_ID#####
     server_ID#####
     server_ID#####
instance_ID#####
     dispatcher_ID#####
     server_ID#####
     server_ID#####
So, instance_12345 is the equivalent of physical host. The dispatcher that runs on the java app server, dispatcher_ID12345, makes the decision which server (server_ID12567 vs server_ID12678) to route a request to. My question is does anyone know of a way to directly address server_ID12567 versus server_ID12678. Again, this is needed for administrative troubleshooting puposes only.

Scheduling web intelligence reports from SAP EP Portal : Server Side Trust

Hello,
We have set-up SSO between SAP EP 701, SAP BI 701 and Business Object XI 3.1 to allow users to access reports without having to sign-on again as explained here :
/people/ingo.hilgefort/blog/2008/09/19/businessobjects-and-sap--configure-sap-authentication
But, we have recently been contacted by some users because when scheduling Webi Report from a link within the portal they have the following errors :
u201CA database error occured. The database error text is: Unable to connect to SAP BW server System received an expired SSO ticket. (WIS 10901) u201D
The user told us that he doesn't encounter the error when :
Login in directly to the BO Infoview (without SSO from the SAP Enterprise Portal.)
The first Webi scheduling is succesful from the portal (I suppose because the portal token is still valid)
I understand that we also have to configure the Server Side Trust between BO Enterprise server and the SAP BI7 backend as explained here , but I do not really understand its purpose
https://websmp106.sap-ag.de/~sapidb/011000358700001646962008E/XI3-1_BIP_SAP_INSTALL_EN.pdf
I've found a similar discussions here ;
Issue with SAP Single Sign-On and Scheduling Reports
I still have some questions :
If we configure the Server Side Trust between BO Enterprise server and the SAP BI7 backend .
The Portal Logon ticket will remain an issue at some point of time , does it mean tha the WeBi report job sheduling should not be perfromed from the SAP EP Portal ?
We haven't configured the Server Side Trust , yet the users told us that they are able to schedule webi report directly from the BO Infoview ? How is it posible ?
Thank you in advance for your help.
Regards.

Thank you Mr Hilgefort for your detailled explanations.
I now have to provide some explanations to my managers, and to be honest , there are still some points that
are unclear to me, and it would be extremely helpful if could confirm (or not) the follwoing points.
When scheduing Webi report from the sap portal, we're getting SSO errors.
SAP provide the follwoing note explaining how to extend the validity of the J2EE token (Portal token), but this is not a long term solution, at certain point of time the ticket will expire. Webi shceduling should not be perfromed from the Portal.
Sap note 1352127 - Scheduled Webi report fails with: A database error occurred. The database error text is: Unable to connect to SAP BW server System received an expired SSO ticket
Webi Scheduling should be performed from BO Infoview. SNC should be configured between BO server and SAP BI7.0 backend.
We should Configure Server SNC as explained in the BusinessObjects XI Integration for SAP Solutions Installation and Administration Guide at Chapter "Configuring SAP for server-side trust". (1341043)
The SAP Portal is not involved here and is not an option even with the configuration of SNC/Server side trust.
thank you for your patience.
Best Regards.

How to create one more server node for SAP J2EE server?

Hi,
Can any one please suggest how to create one more server node for SAP J2EE server? I am using WAS700.
Thanks and Regards,
Smriti.

Hai,
Login into the Configtool(C:\usr\sap\SID\DVEBMGS<inst no>\j2ee\configtool) if ABAP+JAVA stack or C:\usr\sap\SID\JC<inst no>\j2ee\configtool) if JAVA stack
click on the instance and and select the addserver button on the top to create a servernode for J2EE server.
Thanks and Regards,

500 Internal Server Error on opening Business Planning in SAP Portal 7.3

Dear All,
While trying to start working with Business Planning role in SAP Portal 7.3, I am getting the following error message.
Please Help.
Detailed Exception
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session DMm9txY6YHo3d0c6cKZ9Bw--DWk64skeumguWcqfCg_Y9A--. The causing exception is nested. RID=fb772c5cd67111e3ca7d0000015894b2
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:663)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:349)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.tc.webdynpro.services.exceptions.ApplicationFaultException: wdDoInit: exception thrown in this user coding area
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:164)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:590)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1457)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:660)
... 46 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load the object: pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/Roles/com.sap.ip.bi.business_planning_showcase/com.sap.ip.bi.planning/com.sap.ip.bi.Planning_Overview with user jelbin
at com.sap.portal.pb.data.PcdManager.initialContextLookup(PcdManager.java:129)
at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:55)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:622)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:227)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:137)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
... 52 more
Caused by: javax.naming.NamingException: Failed to lookup External Link for: portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/Roles/com.sap.ip.bi.business_planning_showcase/com.sap.ip.bi.planning/com.sap.ip.bi.Planning_Overview [Root exception is com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed to lookup External Link for: portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/Roles/com.sap.ip.bi.business_planning_showcase/com.sap.ip.bi.planning/com.sap.ip.bi.Planning_Overview]
at com.sap.tc.pcd.proxies.JndiProxy.getObjectInstance(JndiProxy.java:121)
at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:962)
at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:742)
at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:121)
at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1824)
at com.sapportals.portal.pcd.gl.url.BaseURLContext.lookup(BaseURLContext.java:265)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sap.portal.pb.data.PcdManager.initialContextLookup(PcdManager.java:125)
... 57 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed to lookup External Link for: portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/Roles/com.sap.ip.bi.business_planning_showcase/com.sap.ip.bi.planning/com.sap.ip.bi.Planning_Overview
at com.sap.portal.pcm.iview.admin.PcmIviewCommon.getExternalLinkApplication(PcmIviewCommon.java:277)
at com.sap.portal.pcm.iview.admin.PcmIviewCommon.initLayers(PcmIviewCommon.java:135)
at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:177)
at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:131)
at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:642)
at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:378)
at com.sap.tc.pcd.proxies.JndiProxy.getObjectInstance(JndiProxy.java:69)
... 65 more
Kind Regards,
Jelbin

Hi Cornelia,
With the link Planning Modeler and Planning Wizard should be opened.
I mean if we click on Start Modeler button in transaction RSPLAN, the link should redirect us to Planning Modeler.
And if we click on Start Wizard button in the transaction RSPLAN, the link should redirect us to Planning Wizard.
Regards,
Jelbin

Need Documentation on how to intehrate Exchange server 2007 with SAP portal

hi,
i need some documentation on how to integrate microsoft Exchange server 2007 with SAP portal.
can anybody help?

Hi Payel,
Pls check the links below..
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/7a/ec015c8446d447a83776d40f31c84f/content.htm">Link</a>
Note : As specified in the document, only the following versions of Microsoft Exchange server are supported:
● Exchange Server 2000
● Exchange Server 2003
Regards,
Venkat.

TREX on Portal-Server also used for search/index for SAP Records Management

Hi all,
can a installation of the TREX on the Portal-Server (or as separate Server) used for Portal Index/search and also in parallel for searching of Content in an SAP Records Management (means full text research of records/ dossier in the SAP RM) ? Some ideas, tips or settings to keep in mind ?
THX
mario

Hi Neil,
We have exactly the same problem. We installed a new SAP E-Commerce system on Microsoft Windws 2008 R2 with TREX Version 7.10.43.00. The TREX connection is okay. Also the catalogue replication works without any problems. The SAP support means it is a permission problem on the IIS. The problem isnu2019t solved yet and the message to the SAP support is in process.
What is your effect with this link?
http://localhost:<TREXNAMESERVER>/TREXHttpServer/
Default:
http://localhost:<30305>/TREXHttpServer/
Kind regards,
Roland

SAP Portal server node identifier

Similar Messages

Maybe you are looking for