SAP NW Newbie

I just came across this application designed for late-night computer users. The application adjusts the monitor's display colour with time, making it look bright at day and warm at night. You may want to change the transition speed to slow and slide the night lighting towards right. You can even disable it for an hour if you are doing any color-sensitive work. Download link: http://stereopsis.com/flux/ If you do not like f.lux and want to uninstall it, slide the night light to the extreme right and then uninstall it.

Most of the developers tend to use the same File server and directory location to test their File Senders. This can result in a file being accessible to more than one File Sender (this is possible if the ftp server, source directory and file name are same). While testing the Channel, if you find that the file is processed, but you don't find anything in CC Monitoring screen, it is likely that the file is being picked up by some other CC. One can avoid this situation by using a seperate directory for the File Sender Channel. Basis Admins may check config_<channel name>_<service name>_<party name>.txt files in <path_to_serverN>/log/services/com.sap.aii.adapter.file.svc to see if a file is accessible by multiple CCs. The config_<channel name>_<service name>_<party name>.txt files are dumps of the File channel configurations available on the XI system. Similar files, for JDBC channels can be accessed from <path_to_serverN>/log...

SAP Note 967812 lists the mandatory Services and Application required on XI. The same are listed here. Dispatcher/Server Service Name (Visual Admin) Service Name (Configtool) Mandatory? Impacts if the service is disabled? d/s ABAP Communicator r3startup mandatory for XI d/s Administration Adapter adminadapter mandatory for J2EE s Application Client appclient not mandatory CTS will fail s Application Locking applocking mandatory for XI d/s Basic Administration basicadmin mandatory for J2EE d/s Classloader viewer classload mandatory for XI s Classpath resolver classpath_resolver mandatory for XI d/s Configuration Adapter configuration mandatory for J2EE s Connector Container connector mandatory for J2EE s Deploy deploy mandatory for J2EE s Destinations tc~sec~destinations~service mandatory for XI s Distributed Statistics dsr not mandatory No J2EE statistical data will be gathered. s EJB Container ejb mandatory for XI s File Service file mandatory for J2EE d/s HTTP Pr...

JARM collects response time of application which may be helpful in troubleshooting performance problems to improve user experience. However JARM itself causes performance overhead for data collection . It may be turned on for troubleshooting and kept off during normal use by performing the following steps: 1. Logon the j2ee engine via Visual Administrator. 2. Go to server_XXX -> services -> Performance Tracing. 3. Select the properties tab 4. Change value of property jarm/switch from on to off, then press update and save for all nodes.

If you have restrictions on the maximum heap memory that can be allocated for J2EE engine, chances of OOM error can be reduced by reducing maximum message size and messages/mappings that can be processed in parallel. Following are few suggestions: 1. Reduce the number of parallel mappings. Reduce "Number of Connections" for the destination AI_RUNTIME_JCOSERVER in JCo RFC Provider service. This will reduce the maximum number of simultaneous mapping requests that can be made, reducing memory consumption. 2. Reduce the number of threads allocated for each adapter. By reducing the number of threads allocated for each adapter, the number of messages that are processed in parallel can be reduced. You can control the thread allocation for each adapter by customizing messaging.connectionDefinition property in the service SAP XI AF Core.   Check http://sapnwnewbie.blogspot.com/2010/10/threads-per-adapter-type-and-receiver.html 3. Reduce the time interval within which the ...

SAP has provided Web Diagtool that lets you set trace levels on a few locations and collect the information as zip file. It is much convinient to use diagtool compared to log configurator when the problem can be reproduced on demand. Once you have deployed the sda file attached to SAP Note 1045019, you can call the diagtool using http://<host>:<port>/diagtool Usage: 1. Open http://<host>:<port>/diagtool 2. Select "All" for "Component" 3. Using the "Search Pattern", add the location on which you would like to collect the trace 4. Press Start. 5. Reproduce the problem 6. Press Stop, when the error occurs. 7. The trace is presented as html. You can also downalod the trace as a zip file. - You may have to increase "Maximum number of collected records" property if you wish to run the tool for a long duration. - Before starting the diagtool, make sure you are ready to reproduce the problem. The following...

Copy the iaik_jce.jar or iaik_jce_export.jar from the SCS Instance \\<HOST>\SAPMNT\<SID>\SYS\global\security\lib\tools\iaik_jce.jar to your CI \usr\sap\<SID>\JC<Inst. Nr.>\j2ee\admin\lib