CTS+ Confguration for Portal Transports

CTS+ Confguration for Portal Transports

Use:

Enhanced Change and Transport System (CTS+)  helps us to transport Java objects and SAP-related non-ABAP applications in the system landscape, alongside ABAP objects. we can also administer non-ABAP systems during a CTS transport domain in SAP NetWeaver Application Server ABAP.

Transportable Objects:

You can use CTS+ to move the subsequent additional objects:

•Java-based and J2EE-based objects:

 Software Component Archives (SCAs)
 Enterprise Application Archives (EARs)
 Software Deployment Archives (SDAs)

•SAP NetWeaver usage type SAP NetWeaver Portal (EP) objects:

 Enterprise Portal Archives (EPAs)
 Enterprise Portal Applications (PARs)
 Knowledge Management objects (KM Content and KM Configurations)

• SAP NetWeaver usage type PI (Process Integration) Non-ABAP objects:

 Integration Builder objects (TPZs)

Objects related to SLD content  (products, software components, technical systems, and business systems)

Configuration – Concept:

The following three components must be configured before you'll use the improved Change and Transport System.

• CTS Deploy Web service (SAP NetWeaver AS Java)

This is a Java Web service liable for communicating with the deployment tools in non-ABAP systems. The transport control program tp communicates with the 

CTS Deploy Web service when deploying the non-ABAP objects.

• CTS Deploy proxy (SAP NetWeaver AS ABAP)

A CTS Deploy proxy is required on the ABAP side to enable the transport control program tp on SAP NetWeaver AS ABAP to communicate with the CTS Deploy Web service on SAP NetWeaver AS Java.

• Transport Organizer Web UI (SAP NetWeaver AS ABAP)

This is an Web Dynpro ABAP application during which you create and edit transport requests for non-ABAP systems.

Configuring the CTS Deploy Web Service:

Use:The CTS Deploy Web service connects the ABAP transport tools to the deployment tools within the non-ABAP applications.

Prerequisites:

This deployment Web service has been a part of SAP NetWeaver 7.0 since Support Package Stack 12.

Information about using the CTS Deploy Web service in another SAP NetWeaver system is out there in SAP Note 1003674.

Checking the CTS Deploy Web Service:

1.  Open the CTS server in SAP NetWeaver Application Server Java,.
2. In your Web browser, enter the following URL:
3. Open Web Service Navigator.

The DeployProxy Web service is within the list of deployment Web services.

Note: Deploy the patch DI CHANGE MGMT SERVER 7.00 as per the SAP Note no: 1076189 if you couldn’t find the service

Configuring the HTTP Connection:

You should be in SAP NetWeaver Application Server ABAP in your CTS system.

1. Call transaction SM59.
2. Create a new HTTP connection called CTSDEPLOY.
3. Choose the Technical Settings tab page.

 a. Enter the name of the target host, the service number (500), and therefore the path prefix /DeployProxy/default?style=document. Confirm by choosing Enter.

 b. If you see any warnings about invalid query strings or missing documentation, ignore them by choosing Enter.

 c. Save your entries.

4. Choose the Logon and Security tab page.

 a. Select Basic Authentication as the logon procedure.

 b. Enter a J2EE user name and password.

 c. Save your entries.

5. to check the new HTTP connection, choose Connection Test.
6. Choose Continue to confirm.

If you've got created the new HTTP connection successfully, the status text within the test results is about to OK.

Setting a Timeout for the Deployment:

Use:Large objects can cause timeouts in deployments. set more time out duration  than the longest expected deployment time.

Procedure:
You should be in SAP NetWeaver Application Server ABAP in your CTS system.

1. Call transaction SM59.
2. select HTTP Connections to External Server ® CTSDEPLOY.
3. Select the Special Options tab page.

The ICM Default Timeout option is chosen because the default under Timeout.

Select a timeout that's above the longest expected deployment. If unsure , select No Timeout to avoid the connection timing out during a deployment.

Configuring the Logical Port for the Web Service:

Use:Logical ports for Web services are Customizing objects.

Prerequisites:

To configure a logical port, you want to enable Customizing changes to be made in client 000. You can cancel these changes once you've got configured the CTS Deploy Web service.

Setting the System Change Option:

You should be in SAP Net Weaver Application Server ABAP in your CTS system.

1. Call transaction SE03.
2. select Administration  -> Set System Change Option and click on Execute.

 The System Change Option screen appears ->
3. Choose Client Setting.

 The Display “Clients” View: Overview screen is displayed.

4. Select the client 001(The client which you're getting to use for CTS+ Transport Requests).

5. Choose Change ® Display.

A panel with the messageCaution: The table is cross-client. appears.

6. Choose Continue to confirm.

7. Make the following changes:

 a. Choose Detail.

 The Display “Clients” View: Detail screen is displayed.

 b. Select Automatic Recording of Changes.

8. Save your entries.


Creating a Logical Port:

You should be in SAP Net Weaver Application Server ABAP in your CTS system.

1. Log on to client 000.

2. User must be aside from DDIC and SAP*.

3. Call transaction LPCONFIG.

 The Display/Create Logical Port screen is displayed.

4. choose the proxy class CO_TFLDEPLOY_PROXY_VI_DOCUMENT from the proxy list.

5. Enter CTSDEPLOY as the logical port.

6. Choose Create.

 The Edit Logical Port screen is displayed.

7. Enter an outline for the logical port and choose the Default Port checkbox.

8. Under General Settings, choose the decision Parameters tab page.

9. Select CTSDEPLOY as the HTTP destination.

10. Save your entries.

 A panel is displayed that prompts you to specify a customizing request.

11. Enter your changes in a change request.

12. Activate the CTS Deploy Web service logical port .


Activating the online Service for Transport Organizer Web UI:

Use:To sign up non-ABAP objects to a transport request, you want to activate the online service CTS_BROWSER.


Prerequisites:

• You have authorization for transaction SICF.

• Ensure to activate all ICF services required to run an ABAP Web Dynpro application.


Note: For more information, see SAP Note 517484.

Procedure:

1. Call transaction SICF. This transaction is a cross-client transaction.

2. Enter SERVICE within the Hierarchy Type field and CTS_BROWSER within the Service Name field.

3. Choose Execute

4. Select the online service (CTS_BROWSER) on the Maintain Services screen.

5. Activate the online service by opening the context menu (secondary mouse button) and selecting Activate Service.

A dialog box for activating IFC services is displayed.

6. Choose Yes (with tree icon).


If you would like to check the online service, open the context menu (secondary mouse button) and choose Test Service.


Starting Transport Organizer Web UI:

Use:You must start Transport Organizer Web UI before you'll begin editing and organizing your transport requests.

Prerequisites:

You have set the parameter NON_ABAP_WBO_CLIENT.


Procedure:

1. go online to the SAP system client with the user and password that you simply want to use to start out Transport Organizer.

2. To start Transport Management System (TMS), call transaction STMS.

3. to try to to this, choose Environment -> Transport Organizer Web UI.

 This starts Transport Organizer Web UI for the client to which you're logged on.

4. within the System panel , choose the system ID of the system that you would like to organize your transport request. This is usually the development system.

5. In other way, you'll use below URL to open Transport Organizer Web UI:

http://:/sap/bc/webdynpro/sap/cts_browser?SYSID=


Customizing for Application Types:

Use:The application type is only a display attribute and doesn't determine the deployment method. Application types are utilized in the CTS_BROWSER Web Dynpro to classify attached objects. You can also add your own application types manually within the table CTS_RQ_APPLID.


Procedure:

1. Call transaction SE16.

 The Data Browser: Initial Screen appears.

2. In the Table Name field, enter CTS_RQ_APPLID.

3. Choose Table Contents or Enter.

 The Data Browser: Table CTS_RQ_APPLID: Selection Screen appears.

4. Click on  Execute button leaving the application field empty.

 The Table CTS_RQ_APPLID screen appears.

5. Click on Create button if the application type doesn’t exist.

 The Insert Table CTS_RQ_APPLID screen appears.

6. Enter the name of the application within the Application field.

 When you choose the F4 help within the Application field, the application name you entered appears within the list box.

7. Enter an outline of your application type within the Description field.

8. Save your entries.


Defining and Configuring Non-ABAP Systems:

Use:When you create a transport landscape in Transport Management System (TMS), you define how you want objects to be transported between systems in the different phases (development, quality assurance, and production) of the software lifecycle.


Prerequisites:

You have configured the CTS Deploy web service.

Creating Non-ABAP Systems:

You are in your TMS domain controller.

1. Call transaction STMS.

2. Choose System Overview.

3. Select SAP System -> Create -> Non-ABAP System.

 The TMS: Configure Non-ABAP System panel is displayed.

4. Create the non-ABAP system with a system ID and an outline .

5. Select the CTS system because the communication system.

6. Make the following settings, depending on whether your system is a source system or a target system (or both):

 o Non-ABAP system as source system

 Under Source System Settings, select the Activate Transport Organizer flag and enter the client where you would like to use Transport Organizer.

 o Non-ABAP system as target system

 Select the Activate Deployment Service flag under Target System Settings, Select the preferred deployment methods filling out the remainder of the fields accordingly.

7. Provide system user and password for your preferred deployment methods.

8. Save your settings and ensure that you simply want to distribute the TMS configuration.

All parameters and their values will automatically be generated bu the system now by default. To display these parameters, select your system within the system overview and choose the Transport Tool tab page.


Configuring Transport Routes:

1. Goto STMS and choose Transport Routes in Overview menu

2. it'll open below window to configure Transport Routes. Change to Edit Mode as below

3. In Menu Option: Configuration -> Standard Configuration -> Select appropriate Configuration option consistent with your landscape requirements.

 Here we have selected Development and Production System.

4. Provide both Development System and Production system SIDs 

5. it'll create Transport Routes in between above two mentioned systems. Save the configuration.

6. In the popup screen click Yes to distribute and Activate the configuration.


Configuring the Destination Service:

Use:You must first use RFC to connect your SAP application system ( before you can attach objects to transport requests directly in the application;such as SAP NetWeaver PI or SAP NetWeaver Portal) to the CTS server. This enables your application to talk with the transport system.


Prerequisites:

• You have change authorization in Visual Administrator.

• you've got a user with the acceptable authorizations in SAP NetWeaver Application Server Java.


Procedure:

1. Open Visual Administrator in SAP Application Server Java.

2. Opt Cluster -> Server -> Services -> Destinations.

3. Create an RFC connection naming it as sap.com/com.sap.tc.di.CTSserver by choosing Create.

4. Under Connection Settings, provide the connection data of the CTS server.

5. Under Logon Data, select the present User (Logon Ticket) option as authentication for the connection to your CTS server. We recommend that you use Single Sign-On (SSO).

If you can't use SSO, select the Configured User option and enter your preferred language, a client, and an appropriate user and password.

Enter the client entered within the parameter NON_ABAP_WBO_CLIENT in TMS.

6. Under Repository Connection and Pool Settings, use the default settings.

7. Save your entries.

If you would like to check the connection, choose Save and Test.


Choosing a Transport Strategy:

Use:You can influence the behavior of the transport system once you create and release transport requests by configuring the strategy parameters. In this manner, we can provide optimum support for your chosen transport process (automatic or manual creation and release of requests).

You only require these parameters for applications that have a close coupling with the CTS system (such as SAP NetWeaver Portal systems and SAP NetWeaver PI systems).

Prerequisites:

You have configured the connection between your application and therefore the CTS server.

Procedure:

1. Call transaction STMS.

2. Choose Overview ® Systems.

3. Select a system.

4. The screen Display TMS Configuration: System appears.

5. Choose the Transport Tool tab page.

6. Switch to change mode.

7. Add the following parameters:


o WBO_GET_REQ_STRATEGY - smart

Once you export an object from an SAP NetWeaver portal system or an SAP NetWeaver PI system, transport request will be automatically created.

The following values are possible:

§ Smart

The system creates a transport request (if not already available) and flags it because the standard request.

§ Tagged

This is configured because the default value within the system. You must have created a transport request already in Transport Organizer Web UI and flagged it because the standard request.


o WBO_REL_REQ_STRATEGY - Manual

Transport request will be automatically released  in an SAP NetWeaver portal system or an SAP NetWeaver PI system.

The following values are possible:

§ Auto

Transport request will be released automatically from the system as soon as an object is added to the request in an SAP NetWeaver portal system or an SAP NetWeaver PI system.

§ Manual

This is configured because the default value within the system. You must release the transport request manually or set the worth of the parameter to Auto.


Create Transport Request using Transport Organizer Web UI

1. Use below URL to access Transport Organizer:

'Protocol'://'server':'Web AS Port'/sap/bc/webdynpro/sap/cts_browser?SYSID='SID of Development System as Configured in TMS'

E.g.: http://pwdf4156.wdf.sap.corp:8002/sap/bc/webdynpro/sap/cts_browser?SYSID=CAI

2. Transport Organizer will look like below. Click on Create Request to create new Request.

3. Mention Short Description and Owner of Request. Project field can be left blank.

4. Click on Attach Object to connect non ABAP Object to move Request.

5. In crop up window, select Client and Browse for the file and click on on OK

o Client: look for the file on your desktop and ensure by choosing OK.

o Server: Search the directory defined within the parameter NON_ABAP_WBO_INBOX for the acceptable source system. In the directory, select the file and confirm by choosing OK.

6. you'll check the attached Non-ABAP Object in Object List Tab as below:

7. Now click on Release to Release the Request to move Queue.

Document References:

1. https://websmp108.sap-ag.de/changecontrol

2.http://help.sap.com/saphelp_nw70/helpdata/EN/45/ec25370fdc3481e10000000a1553f6/frameset.htm

ASSERTION_FAILED dump and solution in SAP APO/BW

Below answer is for fixing ASSERTION_FAILED dump  in APO and BW systems.

Procedure:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' Table with the following choice parameters:

GROUPID   =  'space'
GROUPTYPE =  'space' or 'S'
REF_RULE  <> 'space'
If you see  inconsistent entries in the RSTRANRULE Table like:
TRANID        *
OBJVERS      *
RULEID         *
SEQNR          *
GROUPID      00
GROUPTYPE  space  or  GROUPTYPE    'S'
RULETYPE      space
REF RULE       *

Remove these entries from the table.

Activate the affected Changes.

Check if dump nevertheless occurs. 

Owners and authorizations for BR*Tools

The following setup is essentail to call the BR*Tools with out any error, especially while using transaction DB13 or DBACOCKPIT:

(1) ora and adm groups on DB server have a search path on /sapmnt//exe.

(All br* are contained in this directory.)

ora belongs to the dba group,

adm belongs to the sapsys group,


(2) adm group on the DB server has the rhosts entry: "+ adm".


(3) The ops$adm Oracle user has to be created within the DB and should have the sapdba role (not DBA!) (refer SNote 134592 for more information about the role).


(4) brarchive, brbackup, and brconnect belongs to ora and should have authorization 4775:

-rwsrwxr-x ora sapsys ...


Reason:

Both the operating system &#40;OS&#41; user ora and the OS user adm (for example, from SAP R/3, transactions DB13 or DBACOCKPIT) must be able to call these tools. These tools require access authorization to the database directories and files also on the log directories (saparch,

sapbackup, sapcheck, and sapreorg) of the BR*Tools. To ensure that they will be executed by both ora and by adm, they need to belong to the user ora, and therefore the s-bit must be set.

(5) brrestore, brrecover, brspace, and brtools belongs to adm and should have authorization 755:

-rwxr-xr-x adm sapsys ...

Reason:

These tools could also be used only by OS user ora, but not by adm. This ensures that the user adm doesn't have write authorization for the log directories and thus cannot create any logs. For this, no s-bit is about , and it's not necessary to define an owner aside from the standard owner adm.

If the tools were started using adm, they might terminate immediately after the beginning thanks to the missing log authorization. However, the user ora can start the programs despite this and also has the specified authorization for the log directories.

Java (Channel/Thread) Lock Administration in PI/PO

SAP PI/PO contains numerous communication channels thorough which they process the messages between SAP to SAP and SAP to Non-SAP systems also.
Sometimes these channels are going to be locked thanks to several reasons which require to be fixed to permit the PI system work perfectly.
Follow below procedure to fix the issue.

Login to nwa portal with below link .

http://:500/nwa

Login using your valid and authorized credentials

Select Locks option (left side bottom option).
It shows the screen with "java Locks".

Open another browser tab navigating to nwa home as shown below
(http://:500/nwa)

Here you'll search with a lock argument if channel name isn't provided or if you've got channel name you'll look for lock argument using search term as “lock”

Match the lock argument within the Java locks screens.
Get confirmation from user and proceed as shown below for releasing locks
You can see Remove lock option if you decide on just one lock entry.

If you decide on quite one lock entry you'll be ready to see Remove all selected Locks tab to release all the chosen lock entries at a time.

Removing single lock entry.
Removing multiple lock entries

It asks for confirmation and then click yes if you want to release the lock.

Procedure for SBWP autoforwarding in SAP

SBWP (SAP Business Work place) is a workflow inbox for that unique user.
Below technique is for placing up autoforwarding in SBWP

Procedure:

       1.      Call transaction SO36.

       2.      Make the following entries:

User
Enter the name of the user whose docs are to be forwarded.

Forward to
Specify the mail id to which the files are to be forwarded.

Address type of the recipient
Forward from... / to...
Enter the begin and stop (date and time) of the time length in which automated forwarding is to be active.

Choose .

Automatic forwarding should be active now.

Queues stay in status READY in SMQ2

Queues stay in status READY in SMQ2

If you observe a situation where many queues are in READY status, the following
situations can apply:

 1. A resource bottleneck with regard to RFC resources. Confirm with transaction
SARFC.

 2. Long DB loading times for RFC tables. If using Oracle, ensure that SAP Note
1020260 - Delivery of Oracle statistics is applied.

 3. To avoid overloading a system with RFC load, the QIN scheduler only reloads
LUWs from the queues after a certain amount of DIA WPs have finished their
work. This can lead to long waiting times in the queues as explained in SAP Note
1115861 - Behaviour of Inbound Scheduler after Resource Bottleneck. Since PI is
a non-user system, we recommend setting rfc/inb_sched_resource_threshold to 3.

 4. Additional overhead during this step occurs due to every message being blocked
during processing. This is no longer necessary and should be switched off by
setting the parameter LOCK_MESSAGE of category RUNTIME to 0 as per SAP Note 1058915.

Integrating RMAN with a Media Manager on UNIX: Basic Steps

Basic procedure of RMAN Integration with a Media Manager on UNIX: 

On UNIX OS,  media management library will be accessed by Oracle the through the UNIX shared

library libobk.so. This file must exist somewhere within the system path. It is highly

recommended that you simply place libobk.so in $ORACLE_HOME/lib, which is where

Oracle searches first.

You do not got to start or pack up the instance when installing the media

management library.

To integrate the media manager on UNIX:

1. If an old libobk.so symbolic link already exists in $ORACLE_HOME/lib, then remove it before installing the media manager. For example:

% rm $ORACLE_HOME/lib/libobk.so

2. After installation, check your media management vendor documentation to work out where the media management library is installed. For example, assume that the library is installed like  /vendor/lib/oracle_lib.so.

3. Besides the installed media management library to $ORACLE_HOME/lib/libobk.so name is changed, or create a symbolic link to the library called libobk.so. For example, you can create a symbolic link to the library as follows:

% ln -s /vendor/lib/oracle_lib.so $ORACLE_HOME/lib/libobk.so

Alternatively, you'll simply change the name of the library to libobk.so. For example:

% mv /vendor/lib/oracle_lib.so $ORACLE_HOME/lib/libobk.so

How to create a java thread dump

Creating a Java Thread Dump

Procedure

1. Start the SAP Management Console.

2. Locate the process for which you want to create a stack dump in the AS Java Process Table.

3. From the context menu, choose Dump Stack Trace.

Result

The stack dump is written to the std_.out file located in the /usr/sap///work directory.

Note

The location of the stack dumps may differ counting on the Java SDK getting used .

RMAN-06023 no backup or copy of datafile found to restore

If we initiate a RESTORE database with a BACKUP controlfile defining  Flash Recovery Area , RMAN execute and implicit crosscheck and catalog of entire objects within the Flash Recovery Area.

RMAN catalogs any objects within the Flash Recovery Area which can not be registered within the controlfile and if any of this files belongs to an incarnation different from CURRENT incarnation within the controlfile then changes controlfile CURRENT incarnation to the one found within the file that's being cataloged.


This avoids database from restoring backups that belong to old CURRENT incarnation.


RMAN reckon with backup available for being restored if the backup incarnation and CURRENT incarnation in controlfile are identical .

Start/Stop a communication channel from an ABAP program using the external control switch

This blog only provides instructions on the way to start/stop a channel using an ABAP program. All other steps to possess a totally functional channel aren't provided during this blog, attend http://wiki.sdn.sap.com/wiki/display/XI/Step-by-Step+Guides or do an enquiry on SDN to urge a suggestion on that.

Scenario:-

 There is a scheduled job running daily/weekly that makes an outbound enter SAP ECC

 There is a channel in SAP PI scheduled to select up the file created and send it to an external system

By following the instructions below, the report can then be included as a step during a job scheduled in SAP ECC and thus the channel scheduling in PI will not be required.

 External Control Off

In the communication channel monitoring, select the relevant commnunication channel and click on External Control Switch to allow the communication channel to be started/stopped externally. When it’s turned on, it should look as below.

External Control On

Goto SE38 to make a report and paste the code below.

report YTEST_PRGM line-size 1023 message-id Z002.

data: V_URL type STRING,

 CLIENT type ref to IF_HTTP_CLIENT.

data: RESPONSE_CODE type SYSUBRC,

 RESPONSE_TEXT type STRING.

data: FIELDS_TAB type TIHTTPNVP,

 STATUS_CODE type STRING,

 STATUS_REASON type STRING,

 NUMBER type I.

data: W_RESULT type STRING,

 RESULT_TAB type table of STRING,

 RESULT_WA like line of RESULT_TAB.

"Get comm channel status

V_URL = '/AdapterFramework/ChannelAdminServlet?party=*&service=*&channel=Test_CommChannel_ExtCtrl&action=status'.

"Start comm channel

"v_url = '/AdapterFramework/ChannelAdminServlet?party=*&service=*&channel=Test_CommChannel_ExtCtrl&action=start'. 

"Stop comm channel

"v_url = '/AdapterFramework/ChannelAdminServlet?party=*&service=*&channel=Test_CommChannel_ExtCtrl&action=stop'. 

call method CL_HTTP_CLIENT=>CREATE

 exporting

 HOST = HOST "PI system name

 SERVICE = SERVICE "Port number

* PROXY_HOST =

* PROXY_SERVICE =

* SCHEME = SCHEMETYPE_HTTP

* SSL_ID =

* SAP_USERNAME =

* SAP_CLIENT =

 importing

 CLIENT = CLIENT

 exceptions

 ARGUMENT_NOT_FOUND = 1

 PLUGIN_NOT_ACTIVE = 2

 INTERNAL_ERROR = 3

 others = 4.

if SY-SUBRC 0.

 message E000 with SY-SUBRC.

endif.

*set header fields

call method CLIENT->REQUEST->SET_HEADER_FIELD

 exporting

 NAME = '~request_method'

 VALUE = 'POST'.

call method CLIENT->REQUEST->SET_HEADER_FIELD

 exporting

 NAME = 'Content-Type'

 VALUE = 'application/xml'. "; charset=UTF-8' .

*Set request protocol

call method CLIENT->REQUEST->SET_HEADER_FIELD

 exporting

 NAME = '~server_protocol'

 VALUE = 'HTTP/1.0'.

*Update url

call method CLIENT->REQUEST->SET_HEADER_FIELD

 exporting

 NAME = '~request_uri'

 VALUE = V_URL.

*Disable logon popup

CLIENT->PROPERTYTYPE_LOGON_POPUP = CLIENT->CO_DISABLED.

call method CLIENT->AUTHENTICATE

 exporting

 USERNAME = USERNAME "Username

 PASSWORD = PASSWORD "Password

CL_HTTP_UTILITY=>SET_REQUEST_URI( REQUEST = CLIENT->REQUEST

 URI = RESPONSE_TEXT ).

*Send http request to server

call method CLIENT->SEND

 exceptions

 HTTP_COMMUNICATION_FAILURE = 1

 HTTP_INVALID_STATE = 2

 HTTP_PROCESSING_FAILED = 3

 others = 4.

if SY-SUBRC 0.

 call method CLIENT->GET_LAST_ERROR

 importing

 CODE = RESPONSE_CODE

 message = RESPONSE_TEXT.

 message I000(SR) with RESPONSE_TEXT.

 exit.

endif.

*Get http response from server

call method CLIENT->RECEIVE

 exceptions

 HTTP_COMMUNICATION_FAILURE = 1

 HTTP_INVALID_STATE = 2

 HTTP_PROCESSING_FAILED = 3

 others = 4.

if SY-SUBRC 0.

 call method CLIENT->GET_LAST_ERROR

 importing

 CODE = RESPONSE_CODE

 message = RESPONSE_TEXT.

 STATUS_CODE = CLIENT->RESPONSE->GET_HEADER_FIELD( '~status_code' ).

 STATUS_REASON = CLIENT->RESPONSE->GET_HEADER_FIELD( '~status_reason' ).

 concatenate RESPONSE_TEXT '(' STATUS_CODE STATUS_REASON ')'

 into STATUS_REASON separated by SPACE.

 message I000(SR) with STATUS_REASON.

 exit.

endif.

*Get header_fields contents such status code, reason etc

"call method client->response->GET_HEADER_FIELDS

" changing

" FIELDS = Fields_Tab .

clear: W_RESULT.

W_RESULT = CLIENT->RESPONSE->GET_CDATA( ).

refresh RESULT_TAB.

split W_RESULT at CL_ABAP_CHAR_UTILITIES=>NEWLINE into table RESULT_TAB.

loop at RESULT_TAB into RESULT_WA.

 write / RESULT_WA.

endloop.

The following variables should be assigned with proper values:-

Host-PI system name

Service-PI system port number

Username-This must be a user in PI system with the subsequent roles: xi_af_channel_admin_display and xi_af_channel_admin_modify

Password-PI user’s password

"Starting the communication channel

v_url = '/AdapterFramework/ChannelAdminServlet?party=*&service=*&channel=Test_CommChannel_ExtCtrl&action=start'.

"Stopping communication channel

v_url = '/AdapterFramework/ChannelAdminServlet?party=*&service=*&channel=Test_CommChannel_ExtCtrl&action=stop'.

"Get communication channel status

v_url = '/AdapterFramework/ChannelAdminServlet?party=*&service=*&channel=Test_CommChannel_ExtCtrl&action=status'.

URL Parameters 

http(s)://host:port/AdapterFramework/ChannelAdminServlet?party=party&service=service&channel=channel&action=action

party- Recognize the party of the channel to be organized. You can use an asterisk (*) as a placeholder to administer various channels simultaneously

service- Recognizes the communication component of the channel to be administered. You can use an asterisk (*) as a placeholder to administer various channels concurrently

channel- Recognizes the name of the channel to be administered. You can use an asterisk (*) as a placeholder to administer various channels concurrently. 

Action- you utilize the beginning and stop actions to start out and stop the channels. You can use the status action to query the status of 1 or more channels.

Reorganizing Tables with BR*Tools

Use

BR*Tools can be used to reorganize tables online for Oracle database in SAP system.

Note

This article gives an overview on the procedure to reorganize a table with BR*Tools.

For more information on the approach to table reorganization, see:

· Reorganization

· Reorganization Case Study

You can perform the following types of reorganization:

· Reorganize tables online

· Check tables for reorganization

· Clean up tables after aborted reorganization

· Conversion of LONG and LONG RAW fields to CLOB or BLOB online in Oracle 10g or higher

· Stop reorganization (command-line mode only)

· Suspend reorganization (command-line mode only)

· Resume reorganization (command-line mode only)

For more information, see -f tbreorg.

Prerequisites

You cannot perform online reorganization for tables with LONG or LONG RAW fields but you'll convert them to CLOB or BLOB online. After this conversion, you'll reorganize all tables online. For more information, see SAP Note 646681.

Procedure

1. From the command line, start the procedure using BRGUI or BRTOOLS, or :

 BRGUI or BRTOOLS:

i. Choose Segment Management ® Reorganize tables.

BRGUI or BRTOOLS displays the menu BRSPACE options for reorganization of tables, where you specify the choices with which you call BRSPACE.

ii. Set the required options:

Note

If required, in Table names you'll enter the names of multiple tables. You can use wildcards. For more information, look in to “Selecting Objects“ in Segment Management with BR*Tools. You can also specify a list of tables to be processed with reorg_table in the initialization profile init.sap.

In Tablespace names and Table owner, you'll specify multiple objects but you can't use wildcards. BRSPACE processes all the tables within the specified tablespace name(s) or all tables belonging to the required table owner(s). But these entries and reorganization action entry are not mandatory.

iii. Choose Continue.

BRGUI or BRTOOLS prompts you to start BRSPACE.

iv. Choose Continue to start BRSPACE.

¡ Command line:

Enter at least the following command:

brspace –f tbreorg

You can go with additional parameters, including the table names, if required. we can see BRSPACE -f tbreorg for more information.

Note

Whichever way you begin the procedure – with BRGUI or BRTOOLS, or from the instruction – you'll use quick mode if you recognize the ultimate object names, in this case the table names. For more information, see How to Use BR*Tools.

BRSPACE starts and you see a message that has Start of BRSPACE processing. From now on, BRSPACE writes a detail log.

2. If you've got already entered the table names, continue with step 5 (quick mode).

Note

If you've got entered multiple tables, BRSPACE displays as confirmation an inventory of tables for reorganization. If you've got not already made a final selection, you'll make a variety from this list.

Continue with step 5 (quick mode).

BRSPACE displays the Table reorganization main menu.

3. Choose Reorganize tables.

BRSPACE displays the table list:

4. Select a table or multiple tables.

Example

These examples only apply for character mode inputs..

To choose the first three tables within the list, enter 1-3.

To choose the first and third tables, enter 1,3.

To choose the first three tables and therefore the fifth, enter 1-3,5.

To choose all tables, enter 0.

BRSPACE will show the  Options for reorganization of tables.

5. Set the required options:

Note

There is no SQL instruction here because the reorganization is performed in several steps by an Oracle package, which contains multiple procedures.

6. to start out processing with the chosen options, choose Continue.

Results

Check the results in the BRSPACE logs.

· The summary log space.logdisplays the return code.

· The detail log s.tbr displays the details.

For more information on the way to view the logs with BR*Tools, see Showing Logs and Profiles with BR*Tools.

The file ddl.sql is created in the subdirectory of the directory $SAPDATA_HOME/sapreorg if the option –d|-ddl is set to a value other than no. The file contains the Data Definition Language (DDL) statements used for the creation of interim tables during the reorganization. For more information, see Reorganization. If the –d|-ddl option is about to only, then only DDL statements are created and therefore the actual reorganization isn't performed