Embedded Files
Java Control Panel - C:\Program Files (x86)\Java\jre6\bin\javacpl.exe - javaws -viewer
Check Java Version - java -version
ESR.bat - "C:\Program Files\Java\jre7\bin\javaws.exe" http://host:5XX00/rep/start/sso/repository.jnlp
ID.bat - "C:\Program Files\Java\jre7\bin\javaws.exe" http://host:5XX00/dir/start/sso/directory.jnlp
Message Prioritization(Dual)
It provides a way to forward the identity/user context of a message unchanged from sender to receiver. It uses SAP Assertion tickets or SAML (Security Assertion Markup Language) as the exchange format for the user info. User mapping takes place in the back end and, in this way, either the token is forwarded directly to the back end or an X.509 certificate is generated, which is then used in the back end.
principal-propagation-using-sap-assertion-ticket-crm--po731-single-stack
Configure Principal Propagation Using Logon Tickets in PI 7.1
- Transport Level Security
- Message Level Security
Download
Issues
- SFTP addon patch upgrade
- ID object activation
- Cluster Node load Balancing issue - High Availability
- CTS+ - ID object auto activation - Disabled
Adapter Framework(AFW)
- Messaging System - Responsible for persistence and queuing of messages
- Sender Adapter >> Module Processor (CallSapAdapter)>> Messaging System >> Integration Server
- Receiver Adapter << Module Processor << Messaging System << Integration Server
- Every message first pass through Dispatcher queue, which is responsible for the prioritization of messages.
- It will pass the message further to the adapter specific queues once consumer threads are available.
- Messaging System uses 4 queues for each adapter type and theses are responsible for sending and receiving messages.
- Send - queue for sending asynchronous messages
- Receive - queue for receiving asynchronous messages
- Call - queue for sending synchronous messages
- Request - queue for receiving synchronous messages
- Each queue is assigned with 5 consumer thread to process the messages.
- In ICO scenario, all the steps(routing, mapping) are processed by Sender Consumer thread in Sender queue.
- The receiver queues are not used at all in ICO.
- Messaging System is part of Adapter Framework AFW.
- The task of the Messaging System is to persist and assign resources for messages processed on the Java stack.
- Messaging System queues have a configurable amount of so called consumer threads that process messages from the queue.
- The default number of consumer threads is 5 per adapter (JDBC, File, JMS, …), per direction (inbound and outbound) and Quality of Service (asynchronous (EO, EOIO) and synchronous).
- The Messaging System is running on every server node.
- Therefore the maximum number of parallel connections to a backend system can be calculated by multiplying the number of server nodes by the configured number of consumer threads.
- Every message will pass through the dispatcher queue first.
- The dispatcher queue is responsible for the prioritization of messages and will pass the message further to the adapter specific queues once consumer threads for the adapter specific queue are available.
- Therefore if you see a backlog on the dispatcher queue it indicates a resource shortage on one of the adapter specific queues
Google Sites
Report abuse