How to install and configure SAP Webdispatcher

1) Download SAP WEBDISPATCHER executables from service market place

http://service.sap.com/patches under SAP NETWEAVER --> SAP NETWEAVER 04 -->Binary Patches -->SAP KERNEL (32/64Bit, unicode/non-unicode) --> -->Database Independent. Here you can download the kernel packet DW.SAR, this contains the SAP Web dispatcher (sapwebdisp).

2) Create a new directory in G:/usr/sap as sapwebdispatcher

3) Copy files sapwebdisp and icmadmin.SAR into this directory from downloaded DW.SAR

4) Extract icmadmin.SAR using SAPCAR

5) Generation of profile for the first time run command

G:\usr\sap\sapwebdisp>sapwebdisp –bootstrap

6) Then provide input as prompted

rdisp/mshost=hostname1

ms/http_port=8112

Instance number for SAP Webdispatcher = 11

HTTP Port number for SAP WebDispatcher=8011

create configuration for Small(S)

7) It will generate Auth file icmauth.txt

8) Note down the user name and password from that window itself

9) Sapwebdisp.pfl,Add another line for redirecting URLs(Example for EP)

icm/HTTP/admin_0= PREFIX/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt

icm/http/redirect_0 = /prefix=/, TO=/irj/portal,port 51100,HOST=EPHOST

10) Now start the WEBDISPATCHER using

sapwebdisp pf=sapwebdisp.pfl - auto_restart

Now we can access portal using webdispatcher server

11) Now we can access portal using webdispatcher server

http://hostname1:8011/irj/portal

How to export and import RFC information

This can be used to take backup of RFC destinations before systm copy and can be restored once system copy is over.

1) Login to SAP Server with sidadm user
2) create a file with rfcexp.dat with below mentioned data

export
client=771
file="F:\rfcexp.ctl"
Select * from rfcattrib
Select * from rfcdes
Select * from rfcdoc
Select * from RFCSYSACL
select * RSECACHK
select * RSECACTB

3) Run command R3trans -w rfcexp.log F:\rfcexp.dat
4) Export should be over with RC=0
5) For import create file rfcimp.dat with following content

import
file="F:\rfcexp.ctl"

6) Run Command R3trans -w rfcimp.log rfcimp.dat

RFCs should be imported 

QA for PI Systems

Question 1:
How to solve the following error coming in Message Monitoring?
HTTP_RESP_STATUS_CODE_NOT_OK
Answer 1:
Go to transaction SICF  /default_host/sap/xi/engine  double click on service
Now check whether you have entered correct information for the following fields.
Client, user id, password, and language information
Question 2:
How to solve the Status "HOLDING" in RWB?
Answer 2:
Go to RWB --> Adapter Engine --> show additional criteria --> Enter the QUEUE NAME in field "Conversation_ID" (for this you have to first know the queue name from details of the messages having status "Holding".) --> Expand "Configure table columns" --> choose "Conversation ID" and "Sequential Number" --> display. --> Sort the list by ascending order of "sequential number" --> cancel the message whose sequential number is latest and go on canceling in ascending order.
Question 3:
How to solve the following error coming in Message Monitoring?
RuntimeException in Message-Mapping transformatio~
Answer 3:
a. The error is in Message Mapping. Go to the Test tab and test the message mapping with the incoming payload file.
b. Check the source structure with the input file that you are sending to XI. Both structures should be exactly same. I mean all nodes and the node structures.
c. Refresh the cache (both Delta cache and full cache) in SXI_CACHE transaction in PI.
Question 4:
How to solve the following error coming in Message Monitoring?
Obligatory node xxx missing in the IDOC structure xxx
Answer 4:
The error is in Message Mapping. Check the node xxx and make sure all its attributes are mapped properly. For Ex: SEGMENT="1" and BEGIN="1"
Question 5:
The message has been sent from sender to PI or from PI to receiver but nothing is coming in Message Monitoring. Where is the input file?
Answer 5:
The file got stucked in the PI queue. Check the following.
a. qRFC Monitoring: transaction SM58  Click Deregistration  Click Registration
b. qRFC monitor (Outbound queue)  Check the queue and monitor the problem
c. qRFC monitor (Inbound queue)  Check the queue and monitor the problem
Question 6:
How to solve the following error coming in Message Monitoring?
No receiver could be determined
Answer 6:
Problem is in Receiver Determination. Check it. If everything is fine then just edit and change something then remove that change and again reactivate the receiver determination.
Question 7:
How to solve the following error coming in Message Monitoring?
Party and service not defined
Answer 7:
The problem is that the file is not able to get any party or service configured for itself.
Check the structure of input file and confirm that the same structure is assigned to Sender Interface.
Question 8:
How to solve the following error coming in Message Monitoring?
Error while refreshing the XI runtime cache
Answer 8:
The problem is in Cache refresh.
Go to SXI_CACHE, then from Menu - XI Runtime Cache - choose "Start Delta Cache Refresh" (F6) and then choose "Start Complete Cache Refresh" (shift + F6)
Question 9:
a. How to change the namespace "ns1" to "if" in the output file
b. How to change the encoding format in output XML file
Answer 9:
Use the adapter module AF_Modules/XMLAnonymizerBean in your receiving CC. Put its module key as "0" and the module key for CallSapAdapter as "1". The module parameters will be (1) anonymizer.acceptNamespaces = namespace1 if (2) anonymizer.quote = " (3) anonymizer.encoding = ISO-8859-1.
Refer OSS Note 880173.
Question 10:
How to add extra namespaces or namespace instances
Answer 10:
Question 11:
a. I::000 --> This error comes while uploading the IDOC metadata in XI in transaction IDX2
b. XI is not getting authorized by R/3 System
c. "name or password is incorrect. (repeat log on)" error comes while testing the authorization of the RFC destination to SAP R/3 system from SAP PI system (SM59)
Answer 11:
In SAP PI system  Go to transaction SM59  check the user id and password in the "security/logon" tab and make ensure it is the RFC service user id and its correct password is entered.
Also make sure that this user id has following roles.
a. SAP_XI_APPL_SERV_USER
b. SAP_XI_IS_SERV_USER
c. SAP_ALL
Question 12:
After transporting PI objects, the objects are not getting updated / created in the target system.
Answer 12:
Go to transaction SE01 --> Transports --> Global Information --> Transports --> check the error displayed there.
Also confirm that the business systems are ready for source and target system before transportation.
Question 13:
After some changes or modification in SLD....the changes are not reflecting in IR or ID
Answer 13:
Go to IR --> Menu --> Environment --> Clear SLD Data Cache
Go to ID --> Menu --> Environment --> Clear SLD Data Cache
Question 14:
If RWB is not opening and showing some stack problem or authorization problem
Answer 14:
Go to transaction SU01 --> user = XIRWBUSER -->Unlock
Question 15:
While transporting or updating the objects in SLD, if the following error comes..
CIM_ERR_ALREADY_EXISTS
Answer 15:
Go to SLD -> Administration -> Content Maintenance -> Select the following Subset -> All classes, Class -> BCSystem. then delete SAP_BCSystem. Then retry.
Question 16:
How to solve the following error coming in Message Monitoring?
a. NO_RECEIVER_CASE_ASYNC
b. No receiver could be determined
Answer 16:
In the Receiver determination, check if the sender service and interface are same as in the SXMB_MONI --> Receiver Identification --> SOAP Header --> Main --> Sender Service and Interface.
Question 17:
How to solve the following error?
Error Category = XI_J2EE_MESSAGING_SYSTEM and error code = HTTP_TRANSMISSION_ERROR
Answer 17:
1. The file size is big (probably more then 10 MB so reduce the file size or extend the file size constraint in XI and extend the time out limit for the adapters in XI.) It's always better to have the file size in between 1 MB to 5 MB. If size less then 1MB or more then 5MB then performance decrease.
2. JCo call is the call between java stack and ABAP stack. So restart the whole XI system (both JAVA and ABAP stack) and process the file again.
Question 18:
How to solve the following error?
Message interface is not defined in process (Integration Process)
Answer 18:
Go to SXI_CACHE,--> then select the IP --> display active version --> choose the latest version of workflow task --> do "repeat activation" --> do "deployment" --> "testing" --> "execute". The problem is due to the reason that the IP has already been transported to production and then get modified in development so when we transport it again then the newer version of workflow task (WS12340002) is not activated over the older version (WS12340001).
Question 19:
How to maximize the HEAP SIZE?
Answer 19:
First Close the Repository Framework Application.
Then from the main Exchange Infrastructure page (browser) instead opening Integration Repository link save the repository.jnlp to local directory say desktop.
Now open this file with any text editor. You fill see some XML tags. Identify this tag


You can change the max heap size according to your requirement. But this max heap size depends on certain factors such as Operating System as well on the hardware (32 bit or 64 bit) and also on the physical RAM you have from where you run IR. You can give up to 2 GB if it is windows OS. You can check SUN's official site for max heap sizes for different Operation Systems & hardware's.
e.g., for max-heap-size = 1 GB change the above tag value as follows.


Save the JNLP file and open this file either by double clicking or by explicitly with Java Web Start application. In general the directory structure for Java Web start application is "Drive>:\Program Files\Java\j2re1.4.2_XX\javaws\javaws.exe". But by default all JNLP files will be associated with Java Web Start when Java Web Start is installed.
Another way to change Heap size memory is as follows:
Run configtool.exe. (/usr/sap/SID/instanceName/j2ee/configtool)
Under cluster-data ... under instance_IDXXX ... Click on server_IDXXX
On Java Settings section, change Max Heap Size memory to 2048.
Save the changes and close Configtool.
Reboot your system.
Question 20:
How to cancel Integration Process (BPM) and stop the process instance from waiting for new messages?
Answer 20:
Delete the old workflows using transaction SWWL.
Question 21:
How to stop and start BPE?
Answer 21:
Go to Transaction code SWF_XI_ADM_BPE.
Question 22:
How to access Java documents and Source Text for the sample Adapter Module in SAP PI?
Answer 22:
You can find the sample adapter module in the path "C:\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\com.sap.aii.af.sample.ra\connector\connectors\sample_ra.rar".
Question 23:
Can we convert multiple sender values to one receiver value by using "Value mapping group"?
Answer 23:
Yes, you can convert multiple sender values to one receiver value by using "Value mapping group".
Once you are in the "Edit Value mapping Agencies"
a. Put "Sender1" under "Value of " and "Receiver1" under "Value of ".
b. Right click on "Sender1" and select "Value mapping in all agencies".
This will open a new window "Value mapping Group"; therein you can provide multiple sender values (Sender1, Sender2....).
Question 24:
How to transport Alert Categories?
Answer 24:
Go to ALRTCATDEF (In DEV) --> Transport (In TOOLBAR) --> Current Alert Category --> Create a Customizing Request and note down your request number
Go to SE09 (In DEV) --> Check customizing request and Modifiable --> Choose Display Button --> Go to your Request number --> and release the sub node and then release the request.
Go to STMS (In QA) --> Import --> Import your request
With the above method, alerts rules are not transported, you have to create them manually.
Question 25:
How to transport Alert Rules?
Answer 25:
Create a workbench transport request manually with transaction SE09. Delete the corresponding unclassified task of that request. Double click on the transport request and click on button 'edit <-> change'. For Program ID enter R3TR, for Object Type enter TABU and for Object Name enter SXMSALERTRULES.
Now click on the button with the key symbol (located under 'Function'). Click on 'Insert row' and enter * for table key. Save the request, release it and import it in the target system.
Refer SAP Note 1110295
Question 26:
How to solve the following error coming in Message Monitoring?
Interface mapping Object ID ***** Software Component ****** does not exist in runtime cache
Answer 26:
Refresh SXI_Cache and CPACache.
a. To refresh SXI_CACHE, go to transaction SXI_CACHE and click "start complete cache refresh"
b. To refresh CPACache, enter the following URL
http://:/CPACache/refresh?mode=full
Question 27:
How to solve the following error coming in Message Monitoring?
Answer 27:
In the Receiver determination, check if the sender service and interface are same as in the SXMB_MONI --> Receiver Identification --> SOAP Header --> Main --> Sender Service and Interface.
Question 28:
How to solve the following error coming in CC Monitoring?
Error occurred while connecting to FTP server: Peer certificate rejected by ChainVerifier
Answer 28:
Use Fully Qualified Domain Name (FQDN of the FTPS server) (for Ex. Abc.sap.com) instead of IP address (11.22.33.44)
Root cause of problem is the IP to DNS name resolving problem.
Means we are using IP in FTP CC but DNS name (Common name (CN) or Host Name) should be used in FTP CC.
The SSL handshake needs to confirm that the FTPS client is using the FTPS server's DNS name to access the FTP service since only the DNS name of the FTPS server is stored in the certificate signed by the trusted CA (e.g. VeriSign). That does make sense since it's the way the Certification Authorities works.
Briefly, Use Fully Qualified Domain Name (FQDN of the FTPS server) (for Ex. Abc.sap.com) instead of IP address (11.22.33.44)
Question 29:
How to test the alert?
Answer 29:
You can test the alert by executing the report RSALERTTEST.
To check the log, execute the report SXMSALERT_LOGREADER.
Question 30:
How to use OneAsMany function in Message Mapping?
Answer 30:
Let us take an example where the use of contexts can be emphasized.
In the source message shown above OrderNumber appears only once while OrderItem can occur multiple times within the OrderHeader node. Suppose we want to map OrderNumber multiple times in the target message, such that it is available under the target node corresponding to every sales order item. To do this, we can use the node function called useOneAsMany as described below:
a. The first input parameter expects the list of values that we want to propagate to the target message.
b. The second input parameter expects the number of iterations or how many times we want to replicate the value given in the first parameter.
c. The third input parameter is the list of context changes. Depending on this parameter the source values will be propagated to the target after every context change.
Note: For this function to work as expected, the first two parameters must contain the same number of contexts while the last two parameters must contain the same number of values.
Question 31:
How to solve the following error coming in CC Monitoring in RWB?
Mandatory parameter 'xml.keyfieldName': no value found
Answer 31:
In the FCC configuration in Communication channel, you have to provide the following information.
RecordSet Structure = R1,,R2,
Keyfield Name = Key
(Field Key must exist in the Recordset Structures R1 and R2.)
Or
RecordSet Structure = R1,,R2,
R1.fieldNames = F1,F2
R1.keyFieldName = F1
R1.keyFieldValue = V1
R1.fieldSeparator = ;
R1.endSeparator = 'nl'
Question 32:
How to solve the following error coming in Message Monitoring?
Unable to interpret IDoc interface ia_SAP_ABC2SAP_MI
Answer 32:
Check whether the ED (IDOC occurrences have been changed by creating an ED) is used properly in IR and ID.
a. In Message Mapping, use ED
b. In Interface Mapping, use original IDOC
c. In Interface Determination, use original IDOC
Question 33:
If IDOC has been changed in R/3 then what should be done with respect to PI?
Answer 33:
Go to transaction IDX2 --> Delete the old IDOC structure and Load the new IDOC structure
Question 34:
How to solve the following routing error?
NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
Answer 34:
This means no receiver could be found. Check your Receiver Determination. Activate and update cache. Asynchronous messages can be manually restarted.
Question 35:
How to solve the following routing error?
TOO_MANY_RECEIVERS_CASE_BE
Answer 35:
More than one receiver found. Check your ID configuration to ensure that there is exactly one receiver for the synchronous message. Multiple receivers for synchronous interfaces are not permitted.
Question 36:
How to solve the following mapping error?
JCO_COMMUNICATION_FAILURE
Answer 36:
Check whether RFC destination AI_RUNTIME_JCOSERVER is correctly configured
Question 37:
How to solve the following mapping error?
NO_MAPPINGPROGRAM_FOUND
Answer 37:
Ensure that mapping program exists and is activated. If it exists then update the cache.
Question 38:
How to solve the following mapping error?
EXCEPTION_DURING_EXECUTE
Answer 38:
This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
Question 39:
How to process the messages stuck in queues?
Answer 39:
Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
Question 40:
How to solve the following conversion error in message monitoring?
Unable to convert the sender service XXXX to an ALE logical system
Answer 40:
This error occurs in case of scenarios with IDOC adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.
Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service → Adapter Specific Identifiers. Click the button that says 'Compare with System Landscape Directory' and chose Apply. Save and activate your change list.
In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP system's partner profiles.
Question 41:
How to monitor BPM?
Answer 41:
Use the transaction code SXMB_MONI_BPE.
Question 42:
What are the steps that need to be carried out to enable a SAP R/3 System to send IDOC to SAP Exchange Infrastructure?
Answer 42:
1. First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
2. Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
3. To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
4. GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
5. IDOC Tunneling in XI
To prevent performance consuming XMLization and de-XMLization IDOCs are tunneled through SAP XI IDOC adapter meaning no XMLiziation is executed before the IDOC is passed onto the pipeline. Note the message is converted to UTF-8 codepage.
6. Start transaction SXMB_ADM on SAP XI.
Select option Configuration->Integration Engine Configuration and add two parameters EXTERNAL_MAPPER in the category IDOC.
Configure the parameter according to the conditions below:
If Message Code and Message Function are specified in the partner profile:
..ReceiverPort...
If only the Message Code is specified in the partner profile:
..ReceiverPort..
If only Message Function is specified in the partner profile:
..ReceiverPort...
7. Integration Builder  Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
Question 43:
Where can I find aii_map_api.jar to create my Java mapping (if I have the access to OS level)?
Answer 43:
Go to your XI server folders and use this path:
j2ee\cluster\server0\apps\sap.com\com.sap.xi.services
Inside com.sap.xi.services folder you'll find the jar file.
Question 44:
How to download aii_map_api.jar file from market place
Answer 44:
If you want to download aii_map_api.jar from service marketplace, there are two ways:
1. Download SAPXITOOL13P_3-20000274.sca (about 40 MB)
Extract IntegrationServices.sda (with WinZip)
Here you find the aii_map_api.jar
2. Download SAPXIPCK13_0-20000423.sca (about 14 MB)
extract pck.sda
Both files are very big, so you should have a quick connection.
Question 45:
If I do not have the access to OS level then where can I find aii_map_api.jar to create my Java mapping?
Answer 45:
If you don't have the access to your XI/PI server at the directory level or if you don't have access to Market place download,
Then use the below procedure to get the aii_map_api.jar file,
If your machine is running on windows operating system, (remember your machine means from where you work on Repository and Directory Frameworks)
Then look in this folder,
\Documents and Settings
Application Data\Sun\Java\Deployment\javaws\cache\http\D\P\DMrep\DMrepository
Where - host name of XI server.

• J2EE dispatcher port of XI server generally it will be 50000 if instance number is 00 or it will 50000+(100 X Instance number)
• The user profile with which you are working on your machine.

in the directory you will find "RMaii_map_api.jar". Copy this to your working directory for java mapping class program and set in classpath. You can also rename this jar file as the original name is "aii_map_api.jar".
Question 46:
How to solve if java mapping Linkage error occurred?
Incompatible class versions (linkage error)
Answer 46:
The problem "Linkage Error" is due to JDK version mismatch between XI / PI and your Java IDE.
XI uses JDK1.4 so you have to use JDK 1.4 to compile your java code and generate .jar file.
To use different jdk version at netbeans go to your project ----
> right click and than go to properties tab. than at left hand side select libraries
----
at top right select manage platform
--
click add platform
-- select the jdk version here and follow the wizard.
Question 47:
How to perform IDOC and HTTP Adapter Monitoring?
Answer 47:
IDOC and HTTP Adapter resides directly in IS (ABAP Stack) and hence they can not be monitored via transaction SXMB_MONI or from RWB.
IDOC adapter can be monitored from TCODE IDX5
You can test if HTTP adapter is working fine or not as mentioned below.
1. Test the adapter_plain service in TCODE SICF
adapter_plain service can be found under /default_host/sap/xi/adapter_plain
2. TCODE : SMICM and then Shift + F1 and you can see the status of the HTTP server
Question 48:
If each row of the input flat/text file has a different structure, then how to convert text file to XML file?
Answer 48:
If each row of the input flat/text file has a different structure, then it is referred to as complex transformation.
Use SAP standard Module named "localejbs/AF_Modules/MessageTransformBean".
Further help is available inhttp://help.sap.com/saphelp_nw04/Helpdata/EN/24/4cad3baabd4737bab64d0201bc0c6c/content.htm.
Question 49:
Can we integrate Peoplesoft with SAP PI?
Answer 49:
Yes, we can integrate Peoplesoft with SAP PI.
1. Go through these blogs for peoplesoft iWAY adapterhttps://weblogs.sdn.sap.com/pub/wlg/3734 - Part Ihttps://weblogs.sdn.sap.com/pub/wlg/3735 - Part IIhttps://weblogs.sdn.sap.com/pub/wlg/3736 - Part III
2. Another way is to use SOAP Adapter.
Third-party Peoplesoft can send an Asynchronous XML message to PI through SOAP Adapter.
Question 50:
How to get aii_map_api.jar file in PI 7.1?
Answer 50:
The library has been renamed in PI 7.1 as follows.
PI 7.0(3.0) = aii_map_api.jar
PI 7.1 = com.sap.xpi.ib.mapping.lib.jar
You can find the libraries here:
1. com.sap.aii.af.lib.mod.jar = /ext/com.sap.aii.af.lib/lib
2. com.sap.aii.af.ms.ifc_api.jar = /ext/bin/interfaces/com.sap.aii.af.ms.ifc/lib
3. sap.com~tc~logging~java~impl.jar = /system
4. com.sap.aii.af.svc_api.jar = /services/com.sap.aii.af.svc/lib
5. com.sap.aii.af.cpa.svc_api.jar = /services/com.sap.aii.af.cpa.svc/lib
6. com.sap.aii.af.ms.ifc_api.jar = /interfaces/com.sap.aii.af.ms.ifc/lib
7. = /usr/sap//J01/j2ee/cluster/bin

Oracle RMAN Restore : Restoring Lost Database Files from Backup

This section discusses how to restore the different types of database file backed up by RMAN. Once you have an overall plan for restoring the lost parts of your database, look here for details on how to execute the individual tasks in your plan.
This section contains the following topics:

• Restoring the Control File from Backup
• Restoring the Server Parameter File (SPFILE) from Backup
• Restoring and Recovering Datafiles and Tablespaces
• Restoring Archived Redo Logs from Backup

RESTORING THE CONTROL FILE FROM BACKUP

Loss or corruption of all copies of your control file requires restore of the control file from backup. The RESTORE CONTROLFILE command is used to restore the control file.

Note:

After restoring the control files of your database from backup, you must perform complete media recovery of the database as described in "Performing Media Recovery of a Restored Database, Tablespace or Datafile", and then open your database with the RESETLOGS option. The only exception is the case described in "Restore of the Control File to a New Location", where you restore your control file to a location not listed in the CONTROL_FILES initialization parameter. In that case, you create a copy of your control file in the specified location without touching your running database.

RMAN can restore the control file to its default location (determined by rules described in the following section) or to one or more different locations of your choice, using the RESTORE CONTROLFILE... TOdestination option.

6.4.1.1 Default Destination for Restore of the Control File

When restoring the control file, the default destination is all of the locations defined in the CONTROL_FILES initialization parameter. If you do not set the CONTROL_FILES initialization parameter, the database uses the same rules to determine the destination for the restored control file as it uses when creating a control file if theCONTROL_FILES parameter is not set. These rules are described inOracle Database SQL Reference in the description of the CREATE CONTROLFILE statement.

Restore of the Control File from Control File Autobackup

If you are not using a recovery catalog, you must restore your control file from an autobackup. If you want to restore the control file from autobackup, the database must be in a NOMOUNT state. You must first set the DBID for your database, and then use the RESTORE CONTROLFILE FROM AUTOBACKUP command:

RMAN> SET DBID 320066378;
RMAN> RUN {
    SET CONTROLFILE AUTOBACKUP FORMAT 
          FOR DEVICE TYPE DISK TO 'autobackup_format';
    RESTORE CONTROLFILE FROM AUTOBACKUP;
    }

RMAN uses the autobackup format and DBID to determine where to hunt for the control file autobackup. If one is found, RMAN restores the control file from that backup to all of the control file locations listed in the CONTROL_FILES initialization parameter.
For information on how to determine the correct value forautobackup_format, see the description of CONFIGURE CONTROLFILE AUTOBACKUP FORMAT in the entry for CONFIGURE inOracle Database Backup and Recovery Reference
See "Determining your DBID" for details on how to determine your DBID.

Restore of the Control File When Using a Flash Recovery Area

The commands used for restoring your control file are the same, whether or not you are using a flash recovery area. However, if you are using a flash recovery area, RMAN updates a control file restored from backup, by performing an implicit crosscheck of all disk-based backups and image copies listed in the control file, and cataloging any backups in the flash recovery area that are not recorded in the restored control file. As a result the restored control file has a complete and accurate record of all backups in your flash recovery area and any other backups that were known to the control file at the time of the backup. This improves the usefulness of the restored control file in the restoration of the rest of your database.
Tape backups are not automatically crosschecked after the restore of a control file. If you are using tape backups, then after restoring the control file and mounting the database you must crosscheck the backups on tape, as shown in this example:

RMAN> CROSSCHECK BACKUP DEVICE TYPE SBT;

6.4.1.4 Restoring a Control File When Using a Recovery Catalog

Restoring a lost control file from autobackup is easier when using a recovery catalog than when using only the control file to store the RMAN repository. The recovery catalog contains a complete record of your backups, including backups of the control file. Therefore, you do not have to specify your DBID or control file autobackup format.
To restore the control file, connect RMAN to the target database and the recovery catalog, and bring the database to NOMOUNT state. Then issue the RESTORE CONTROLFILE command with no parameters, as in this example:

% rman TARGET rman/rman CATALOG catdb/catdb
RMAN> RESTORE CONTROLFILE;

The restored control file is written to all locations listed in theCONTROL_FILES initialization parameter.
For more details on restrictions on using RESTORE CONTROLFILE in different situations, see the discussion of RESTORE CONTROLFILE inOracle Database Backup and Recovery Reference.

Restore of the Control File From a Known Location

You can restore the control file from a known control file copy using this form of the command:

RMAN> RESTORE CONTROLFILE from 'filename';

The control file copy found at the location specified by filename will be written to all locations listed in the CONTROL_FILES initialization parameter.

Restore of the Control File to a New Location

One way to restore the control file to one or more new locations is to change the CONTROL_FILES initialization parameter, and then use theRESTORE CONTROLFILE command with no arguments to restore the control file to the default locations. For example, if you are restoring your control file after a disk failure made some but not allCONTROL_FILES locations unusable, you can change CONTROL_FILESto replace references to the failed disk with pathnames pointing to another disk, and then run RESTORE CONTROLFILE with no arguments.
You can also restore the control file to any location you choose other than the CONTROL_FILES locations, by using the form RESTORE CONTROLFILE TO 'filename' [FROM AUTOBACKUP]:

RESTORE CONTROLFILE TO '/tmp/my_controlfile';

You can perform this operation with the database in NOMOUNT, MOUNT or OPEN states, because you are not overwriting any of the control files currently in use. Any existing file named 'filename' is overwritten. After restoring the control file to a new location, you can then update the CONTROL_FILES initialization parameter to include the new location.

See Also:

Oracle Database Backup and Recovery Reference for RESTORE CONTROLFILE syntax.

Limitations When Using a Backup Control File

After you restore your database using a backup control file, you mustrun RECOVER DATABASE and perform an OPEN RESETLOGS on the database.
For more details on restrictions on using RESTORE CONTROLFILE in different scenarios (such as when using a recovery catalog, or restoring from a specific backup), see the discussion of RESTORE CONTROLFILE in Oracle Database Backup and Recovery Reference.

RESTORING THE SERVER PARAMETER FILE (SPFILE) FROM BACKUP

If you lose your server parameter file (SPFILE), RMAN can restore it to its default location or to a location of your choice.
Unlike the loss of the control file, the loss of your SPFILE does not cause your instance to immediately stop. Your instance may continue operating, although you will have to shut it down and restart it after restoring the SPFILE. 
Note the following when restoring the SPFILE:

• If the instance is already started with the server parameter file, then you cannot overwrite the existing server parameter file.
• When the instance is started with a client-side initialization parameter file, RMAN restores the SPFILE to the default SPFILE location if the TO clause is not used. The default location is platform-specific (for example,?/dbs/spfile.ora on Linux).
• Restoring the SPFILE is one situation in which a recovery catalog can simplify your recovery procedure, because you can avoid the step of having to record and remember your DBID. This procedure assumes that you are not using a recovery catalog.

RMAN can also create a client-side initialization parameter file based on a backup of an SPFILE.
To restore the server parameter file:

1. If the database is up at the time of the loss of the SPFILE, connect to the target database. For example, run:
   

   % rman TARGET /
   
   

   If the database is not up when the SPFILE is lost, and you are not using a recovery catalog, then you must set the DBID of the target database. See "Determining your DBID" for details on determining your DBID.
2. Shut down the instance and restart it without mounting. When the SPFILE is not available, RMAN starts the instance with a dummy parameter file. For example:
   

   RMAN> STARTUP FORCE NOMOUNT;
   
   

3. Restore the server parameter file. If restoring to the default location, then run:
   

   RMAN> RESTORE SPFILE FROM AUTOBACKUP; 
   
   

   If restoring to a nondefault location, then you could run commands as in the following example:
   

   RMAN> RESTORE SPFILE TO '/tmp/spfileTEMP.ora' FROM AUTOBACKUP;
   
   

4. Restart the instance with the restored file. If restarting with a server parameter file in a nondefault location, then create a new client-side initialization parameter file with the single lineSPFILE=new_location, where new_location is the path name of the restored server parameter file. Then, restart the instance with the client-side initialization parameter file.
   For example, create a file /tmp/init.ora which contains the single line:
   

   SPFILE=/tmp/spfileTEMP.ora
   
   

   Then use this RMAN command, to restart the instance based on the restored SPFILE:
   

   RMAN> STARTUP FORCE PFILE=/tmp/init.ora; # startup with /tmp/spfileTEMP.ora
   
   

Restore of the SPFILE from the Control File Autobackup

If you have configured control file autobackups, the SPFILE is backed up with the control file whenever an autobackup is taken.
If you want to restore the SPFILE from the autobackup, you must first set the DBID for your database, and then use the RESTORE SPFILE FROM AUTOBACKUP command. The procedure is similar to restoring the control file from autobackup. You must first set the DBID for your database, and then use the RESTORE CONTROLFILE FROM AUTOBACKUP command:

RMAN> SET DBID 320066378;
RMAN> RUN {
    SET CONTROLFILE AUTOBACKUP FORMAT 
          FOR DEVICE TYPE DISK TO 'autobackup_format';
    RESTORE SPFILE FROM AUTOBACKUP;
    }

RMAN uses the autobackup format and DBID to hunt for control file autobackups, and if a control file autobackup is found, restores the SPFILE from that backup to its default location.
For information on how to determine the correct value forautobackup_format, see the description of CONFIGURE CONTROLFILE AUTOBACKUP FORMAT in the entry for CONFIGURE inOracle Database Backup and Recovery Reference
See "Determining your DBID" for details on how to determine your DBID.

Creating a Client-Side Initialization Parameter File (PFILE) with RMAN

You can also restore the server parameter file as a client-side initialization parameter file with the TO PFILE 'filename' clause. The filename you specify should be on a file system accessible from the host where the RMAN client is running. This file need not be accessible directly from the host running the instance. This command creates a PFILE called /tmp/initTEMP.ora on the system running the RMAN client:

RMAN> RESTORE SPFILE TO PFILE '/tmp/initTEMP.ora';

To restart the instance using the client-side PFILE, use the following command, again running RMAN on the same client machine:

RMAN> STARTUP FORCE PFILE='/tmp/initTEMP.ora';

RESTORING AND RECOVERING DATAFILES AND TABLESPACES

Restoring a tablespace to its original location and performing media recovery on it is described in "Restore and Complete Recovery of Individual Tablespaces or Datafiles: Scenario". However, you may need to restore a datafile to a location other than its original location if, for example, the disk containing the original location of the datafiles has failed.

Restoring Datafiles from Backup to a New Location

The important step in restoring datafiles from backup to a new location is to update the control file to reflect the new locations of the datafiles. The following example shows the use of the RMAN SET NEWNAME command to specify the new names, and the SWITCHcommand to update the control file to start referring to the datafiles by their new names.
As with restoring datafiles from backup to their original locations, you should take the affected tablespaces offline at the start of restoring datafiles from backup to a new location.
Then, create a RUN block to encompass your RESTORE and RECOVERcommands. For each file to be moved to a new location, use the SETNEWNAME command to specify the new location for that file.
Then, still within the RUN block, run the RESTORE TABLESPACE orRESTORE DATAFILE as normal. RMAN restores each datafile to the location specified with SET NEWNAME, rather than its original location.
After the RESTORE command but before the RECOVER command in your RUN block, use a SWITCH command to update the control file with the new filenames of the datafiles. The SWITCH command is equivalent to the SQL statement ALTER DATABASE RENAME FILE. SWITCHDATAFILE ALL updates the control file to reflect the new names for all datafiles for which a SET NEWNAME has been issued in the RUN block.
This example restores the datafiles in tablespaces users and tools to a new location, then performs recovery. Assume that the old datafiles were stored in directory /olddisk and the new ones will be stored in/newdisk.

RUN
{
  SQL 'ALTER TABLESPACE users OFFLINE IMMEDIATE';
  SQL 'ALTER TABLESPACE tools OFFLINE IMMEDIATE';
  # specify the new location for each datafile
  SET NEWNAME FOR DATAFILE '/olddisk/users01.dbf' TO 
                           '/newdisk/users01.dbf';
  SET NEWNAME FOR DATAFILE '/olddisk/tools01.dbf' TO 
                           '/newdisk/tools01.dbf';
  # to restore to an ASM disk group named dgroup, use: 
  # SET NEWNAME FOR DATAFILE '/olddisk/trgt/tools01.dbf'
  #     TO '+dgroup';
  RESTORE TABLESPACE users, tools;
  SWITCH DATAFILE ALL;   # update control file with new filenames
  RECOVER TABLESPACE users, tools;
}

If recovery is successful, then bring the tablespaces online:

SQL 'ALTER TABLESPACE users ONLINE';
SQL 'ALTER TABLESPACE tools ONLINE';

See Also:

Oracle Database Backup and Recovery Reference for SWITCH syntax

Performing Media Recovery of a Restored Database, Tablespace or Datafile

Media recovery reapplies all changes from the archived and online redo logs and available incremental backups to datafiles restored from backup.
The simplest way to perform media reccovery is to use the RECOVER DATABASE command, with no arguments:

RMAN> RECOVER DATABASE;

You can also perform media recovery of individual tablespaces or datafiles, or skip certain tablespaces while recovering the rest of the database, as shown in the following examples:

RMAN> RECOVER DATABASE SKIP TABLESPACE users;

RMAN> RECOVER TABLESPACE users, tools;

RMAN> RECOVER DATAFILE '/newdisk/users01.dbf','/newdisk/tools01.dbf';

RMAN> RECOVER DATAFILE 4;

RMAN will restore from backup any archived redo logs required during the recovery operation. If backups are stored on a media manager, note that channels must be configured in advance or a RUN block with ALLOCATE CHANNEL commands must be used to enable access to backups stored there.
One very useful option in managing disk space associated with these restored files is the DELETE ARCHIVELOG option, which causes the deletion of restored archived redo logs from disk once they are no longer needed for the RECOVER operation:

RMAN> RECOVER TABLESPACE users, tools DELETE ARCHIVELOG;

Note that when RMAN restores archived redo log files to the flash recovery area in order to perform a RECOVER operation, the restored logs are automatically deleted after they are applied to the datafiles, even if you do not use the DELETE ARCHIVELOG option.
See Oracle Database Backup and Recovery Reference for more details on options for the RECOVER command.

Restore and Recover of a Single Datafile to a New Location:Example

This procedure restores a single datafile to a new location and perform media recovery on it. This lets you restore and recover if the old location is inaccessible because of a problem such as a media failure.

RUN {
    SET NEWNAME FOR DATAFILE 3 to 'new_location';
    RESTORE DATAFILE 3;
    SWITCH DATAFILE 3;
    RECOVER DATAFILE 3;
}

If you want to store a datafile to a new Oracle Managed Files location, you can use this form of the command:

RUN {
    SET NEWNAME FOR DATAFILE 3 to NEW;
    RESTORE DATAFILE 3;
    SWITCH DATAFILE 3;
    RECOVER DATAFILE 3;
}

Oracle will store the restored file in an OMF location, generating a filename for it.

RESTORING ARCHIVED REDO LOGS FROM BACKUP

RMAN will restore archived redo log files from backup automatically as needed to perform recovery.
However, you can also restore archived redo logs manually if you wish, in order to save the time needed to restoroe these files later during the RECOVER command, or if you want to store the restored archived redo log files in some new location.
By default, RMAN restores archived redo logs with names constructed using the LOG_ARCHIVE_FORMAT and the LOG_ARCHIVE_DEST_1parameters of the target database. These parameters are combined in a platform-specific fashion to form the name of the restored archived log.

Restoring Archived Redo Logs to a New Location

You can override the default location for restored archived redo logs with the SET ARCHIVELOG DESTINATION command. This command manually stages archived logs to different locations while a database restore is occurring. During recovery, RMAN knows where to find the newly restored archived logs; it does not require them to be in the location specified in the initialization parameter file.
To restore archived redo logs to a new location:

1. After connecting to the target database, make sure the database is mounted or open.
2. Perform the following operations within a RUN block, as shown in the following example script:
   
   1. Specify the new location for the restored archived redo logs using SET ARCHIVELOG DESTINATION.
   2. Restore the archived redo logs.
   This example restores all backup archived logs to a new location:
   

   RUN
   { 
     SET ARCHIVELOG DESTINATION TO '/oracle/temp_restore';
     RESTORE ARCHIVELOG ALL;
     # restore and recover datafiles as needed
     .
     .
     .
   }
   

Restoring Archived Redo Logs to Multiple Locations

You can specify restore destinations for archived logs multiple times in one RUN block, in order to distribute restored logs among several destinations. (You cannot, however specify multiple destinations simultaneously to produce multiple copies of the same log during the restore operation.) You can use this feature to manage disk space used to contain the restored logs.
This example restores 300 archived redo logs from backup, distributing them across the directories /fs1/tmp, /fs2/tmp, and/fs3/tmp:

RUN 
{ 
  # Set a new location for logs 1 through 100.
  SET ARCHIVELOG DESTINATION TO '/fs1/tmp';
  RESTORE ARCHIVELOG FROM SEQUENCE 1 UNTIL SEQUENCE 100;
  # Set a new location for logs 101 through 200.
  SET ARCHIVELOG DESTINATION TO '/fs2/tmp';
  RESTORE ARCHIVELOG FROM SEQUENCE 101 UNTIL SEQUENCE 200;
  # Set a new location for logs 201 through 300.
  SET ARCHIVELOG DESTINATION TO '/fs3/tmp';
  RESTORE ARCHIVELOG FROM SEQUENCE 201 UNTIL SEQUENCE 300;
  # restore and recover datafiles as needed
  .
  .
  .
}

When you issue a RECOVER command, RMAN finds the needed restored archived logs automatically across the destinations to which they were restored, and applies them to the datafiles.

Hardware Migration

Prerequisites

· Download required software and patches from service market place

· Compare filesystem space with source system database

· Set page memory

Actions on Target server

· Install Oracle RDBMS software

· Apply RDBMS patch to the source patch level

· Install SAP NW2004 with ABAP content

· Install Java add in on ABAP

· Request and Install SAP license for new hardware

· Start J2EE on new server

· Upgrade Kernel to the source patch level

· Take full backup of database

· Take java filesystem backup

· Bring down target server along with DB

· Stop all the services related to oracle and SAP

· Delete data from sapdatas , origlogs and mirrlogs in target system

Actions on source server

· Request Downtime for source server

· Suspend jobs using report btctrns1 in source server

· Bring down application along with DB in source server

· Stop all services related to Oracle and SAP in source server

· Start zipping of sapdatas, origlogs and mirrorlogs

· Zip J2EE filesystem j2EE,SCS, SYS folders.

· Copy the zipped data manually via Wan to target server

Actions on target server

· Unzip the zipped files and place or overwrite them according to the structure

· Change hostname in ABAP according to SAP note 8307

· Change hostname in RZ70

· Change hostname in j2ee config tool according to SAP note 757692

· Start DB,

· Delete source ops$ users and recreate for target server and change the password

· Start SAP and J2EE

· Re Install SAP license

· Reconfigure SMLG,RZ10,RZ04,RZ12, DB13 etc.. accordingly

· Check RFC connections and reconfigure if required

· Reconfigure STMS

· Reconfigure SLD and JCO destinations using visual admin tool.

· Restart cluster for changes to be affected

· Check SLD and portal

· In SLD change hostname in profile and server settings if required

· Reschedule jobs using report btctrns2

· Configure backup strategy

· Take full database backup along with J2EE filesystem.

J2EE SSO Configuration

1. Logon to Visual Administrator -Server=>Services=>Security Provider,

a. select UserManagement tab and the pencil icon.

b. Select Manage Security Stores; highlight UME User Store and EvaluateTicketLogonModule; Click Views/Change Properties.

i. Under Options fill in the Name and Value as follows:

These parameters are in sets with each system that has a relationship to this J2EE engine. The consumer portal is 1, the production client is 2 and the system client is 3. The values for ddn and iss must match the certificates in use on the system.

Name Value

trustedsys1 , 000
trustedsys2 , 100
trustedsys3 , 000
trusteddn1 CN=, OU=J2EE
trusteddn2 CN=, OU=ABAP, O=SAP Trust Community, C=DE
trusteddn3 CN=, OU=ABAP, O=SAP Trust Community, C=DE
trustediss1 CN=, OU=J2EE
trustediss2 CN=, OU=ABAP, O=SAP Trust Community, C=DE
trustediss3 CN=, OU=ABAP, O=SAP Trust Community, C=DE
ume.configuration.active true

ii. Click OK and ignore message about ‘unable to apply to SDK–XMLA Policy Configuration’

c. Select Manage Security Stores; highlight UME User Store and EvaluateAssertionTicketLogonModule; Click Views/Change Properties.

i. Under Options fill in the Name and Value as follows:

These parameters are in sets with each system that has a relationship to this J2EE engine. The consumer portal is 1, the production client is 2 and the system client is 3. The values for ddn and iss must match the certificates in use on the system.

Name Value

trustedsys1 , 000
trustedsys2 , 100
trustedsys3 , 000
trusteddn1 CN=, OU=J2EE
trusteddn2 CN=, OU=ABAP, O=SAP Trust Community, C=DE
trusteddn3 CN=, OU=ABAP, O=SAP Trust Community, C=DE
trustediss1 CN=, OU=J2EE
trustediss2 CN=, OU=ABAP, O=SAP Trust Community, C=DE
trustediss3 CN=, OU=ABAP, O=SAP Trust Community, C=DE

Click OK and ignore message about ‘unable to apply to SDK–XMLA Policy Configuration’

2. Choose Policy Configurations tab and highlight ticket.

a. If the fully qualified name for the login module is displayed, for example, com.sap.security.core.server.jaas.EvaluateTicketLoginModule, then remove the login module (highlight it and choose the remove button below).

b. If you removed it or it didn’t exist, now choose the add button below. You can now choose EvaluateTicketLoginModule and add/re-add it. Position it at the top of the stack (choose the modify button below and use the down arrow (for location) to move EvaluateTicketLoginModule to position 1. Verify the flag SUFFICIENT and the ACL info is correct for EvaluateTicketLoginModule.

c. Check EvaluateAssertionTicketLogonModule - may need to be modified from REQUIRED to SUFFICIENT.

3. Import Consumer Portal certificate:

a. From VA - Using the Key Storage service on the accepting server, select the TicketKeystore view. Choose Load. Select the file from the file system (.crt) and choose OK.

b. The certificate is stored in the selected view as a CERTIFICATE entry.

4. Import ABAP certificate: (same as step 7, just a different file):

a. From VA - Using the Key Storage service on the accepting server, select the TicketKeystore view. Choose Load. Select the file from the file system (_abap.crt) and choose OK.

b. The certificate is stored in the selected view as a CERTIFICATE entry.

Setting Oracle SP File

Q: I am running SAP Netweaver 7 with Oracle 10g. I would like to add new Oracle parameter and delete some parameter base on SAP Notes recommendation. How should I do that?

Answer:

1. You can edit using BRSPACE, by running command from OS: > brspace -f dbparam

2. OR, you can add/edit or delete the parameter from SQL Plus:

ADD / EDIT:

SQL> alter system set “”= scope=spfile;

example: SQL> alter system set “OPTIMIZER_INDEX_COST_ADJ”=10 scope=spfile;

DELETE:

SQL> alter system reset “” scope = spfile sid = ‘*’;

exampler: SQL> alter system reset “_push_join_predicate” scope = spfile sid = ‘*’;

All parameter will be active after you restart the database.

Oracle Metalink access for SAP customers

Do you know that Oracle has an Online Support System like OSS which is called Metalink?

Direct Oracle Customers (SAP Customers  who bought Oracle DB License from Oracle, not from SAP) can access this portal. But what about SAP Customers who bought Oracle License from SAP?

I decided to write this tip, as I see that most of Basis Guys don't know that they are able to access Metalink.

Since 2004, SAP customers who uses Oracle as RDBMS can access this portal with the user provided by SAP.

SAP OSS Note 758563: "Oracle Metalink access for SAP customers" gives the valid users and passwords for Metalink Access. You have to supply a valid Service Marketplace user to display this note.

Sorry that I cannot share this info here for legal reasons.

Note is updated, as some customers tries to delete/lock or change password for these users 

Monitoring – JCmon

Use

The JCmon is a native monitoring program, part of the startup and control framework, which can be used to:

1. Display a list of the processes

2. Enable, disable, and restart the specified processes

3. Shutdown a specified J2EE instance

4. Enable/disable debugging for a specified process

5. Dump stack trace

6. Display a list of the ports used by the J2EE Engine

7. Activate/deactivate debug sessions

8. Increment/decrement the trace level

To start the JCmon, execute the jcmon script file from the /usr/sap///j2ee/os_libsdirectory, where is the system ID of the cluster (for example, C11) and is the instance name of the J2EE instance (for example, JC00). The instance name consists of a prefix (JC or J) and the two-digit instance number afterwards. As parameter for the jcmon script file specify the SAP instance profile:

jcmon pf=/usr/sap//sys/profile/__.

Example:

jcmon pf=/usr/sap/C11/sys/profile/C11_JC00_testpc.

Enter command ‘20’ to display the main menu.

Features

The JCmon main menu provides the following functions:

0: Exit

Returns back to the main menu.

1: Refresh list

Refreshes the process list and the menu.

2: Shutdown instance

Invokes the shutdown of the specified J2EE instance.

3: Enable process

Enables and starts a process, which is switched off. (Restart == no)

4: Disable Process

Stops a running process and switches off the restart flag.

5: Restart Process

Restarts the specified process.

6: Enable bootstrapping on restart

7: Disable bootstrapping on restart

8: Enable Debugging

Checks if the specified process is running in debug mode. If not and the process is configured for debugging, JControl will restart the process in debug mode.

9: Disable Debugging

If the process is running in debug mode, JControl will restart the process and switch off the debug mode.

10: Dump stack trace

The specified process gets an event to invoke the dump of the stack trace of the Java VM. The stack trace is stored in the stderr output file in the work directory.

11: Process list

Displays the status and additional information about all the processes.

12: Port list

Displays a list with detailed information about the ports used by the J2EE Engine.

13: Activate debug session

Activates the debug session for the specified process. To activate a debug session:

1. The process must be running in debug mode.

1. The process must be “Load Balance Restricted”.

14: Deactivate debug session

Deactivates the debug session. The process will be restarted or stopped – this depends on the process configuration.

15: Increment trace level

This increments the trace level for the developer trace file of the specified process (dev_)

16: Decrement trace level

This decrements the trace level for the developer trace file of the specified process (dev_)

17: Enable process restart

18: Disable process restart

-----

98: Synchronize instance properties

99: Extended process list on/off

Activities

For more information, see:

1. Checking that all processes are running

2. Restarting a single process