Just clock the file SQL4SAP.vbs on your sql root dvd
sql;sap;ecc6
Friday, August 21, 2009
Wednesday, August 19, 2009
STMS - Virtual Transport
Virtual Systems are SAP systems that are planned by not yet physically present. In order to subsequently replace a SAP system by a Virtual System use the same SID for both.
You can create a Virtual System through Tramsport Management System tcode STMS.
Why do I need a Virtual System?
In order to replicate the transport routes of the planned system landscape and to ensure that the import queues of the subsequent system already exist.
During SAP Upgrades or when initailly a sand box or development system is available it is required to create a Virtual System in order to store the development and customizing work in the import queues of the respective planned systems.
This is how a Virtual System is created.
1) Log on to the Transport Domain Controller with a user id having full transport authorizations.
2) Using tcode STMS go to Overview=> Systems=>
3) In the Systems Overview choose SAP System=> Create=> Virtual System
4) In the dialog box TMS => Configure Virtual System, enter the name of the SAP system and a description text. Also specify an SAP system as the Communications system for the Virtual System. (By default the Transport Domain Controller is chosen).This system must be already a part of the transport domain. It cannot be a Virtual System or an external system.
5) Distribute the configuration change.
No RFC addresses can be created for virtual systems, so RFC’s are accessed using the transport directory of an already existing SAP system. This system will act as the Communications Systems and the Virtual System will have to always belong to the same transport group as the assoicated Communication System
After the planned system is physically installed it is time to replace the Virtual System with the realized system.
The procedure for the same is as under:
1) Delete the Virtual System from the transport domain
· Using STMS got to Overview=> Systems
· Chose SAP System=> Delete (confirm)
· Distribute configuration change.
As soon as the configuration change is distributed, the virtual system is deleted. The import queue for this system in TMS disappears but it is available as import buffer at the operating systems level.
Now add the new (physical system) to the transport domain:
1) Initialize the Transport Management System on the real SAP System and include the system in the transport domain.
2) Go to the Transport Domain Controller and accept the system. (As the import buffer is available at the operating system level, no change requests will be lost)
3) Distribute the configuration changes.
You can create a Virtual System through Tramsport Management System tcode STMS.
Why do I need a Virtual System?
In order to replicate the transport routes of the planned system landscape and to ensure that the import queues of the subsequent system already exist.
During SAP Upgrades or when initailly a sand box or development system is available it is required to create a Virtual System in order to store the development and customizing work in the import queues of the respective planned systems.
This is how a Virtual System is created.
1) Log on to the Transport Domain Controller with a user id having full transport authorizations.
2) Using tcode STMS go to Overview=> Systems=>
3) In the Systems Overview choose SAP System=> Create=> Virtual System
4) In the dialog box TMS => Configure Virtual System, enter the name of the SAP system and a description text. Also specify an SAP system as the Communications system for the Virtual System. (By default the Transport Domain Controller is chosen).This system must be already a part of the transport domain. It cannot be a Virtual System or an external system.
5) Distribute the configuration change.
No RFC addresses can be created for virtual systems, so RFC’s are accessed using the transport directory of an already existing SAP system. This system will act as the Communications Systems and the Virtual System will have to always belong to the same transport group as the assoicated Communication System
After the planned system is physically installed it is time to replace the Virtual System with the realized system.
The procedure for the same is as under:
1) Delete the Virtual System from the transport domain
· Using STMS got to Overview=> Systems
· Chose SAP System=> Delete (confirm)
· Distribute configuration change.
As soon as the configuration change is distributed, the virtual system is deleted. The import queue for this system in TMS disappears but it is available as import buffer at the operating systems level.
Now add the new (physical system) to the transport domain:
1) Initialize the Transport Management System on the real SAP System and include the system in the transport domain.
2) Go to the Transport Domain Controller and accept the system. (As the import buffer is available at the operating system level, no change requests will be lost)
3) Distribute the configuration changes.
Thursday, July 30, 2009
ECC6 First Page Logo
Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
If successful, your logo will be shown in the Binary data for WebRFC.
Transaction codeSM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name Value to be set
START_IMAGE ZXXXX.GIF
RESIZE_IMAGE NO
Logoff and Login again
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
If successful, your logo will be shown in the Binary data for WebRFC.
Transaction codeSM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name Value to be set
START_IMAGE ZXXXX.GIF
RESIZE_IMAGE NO
Logoff and Login again
Tuesday, July 28, 2009
Configure SAProuter SNC Certificate
1. Use the same account that the SAProuter server runs as
2. stop the router service
3. backup the router folder
4. change to the sap router directory
5. rename or delete these files: certreq, srcert, local.pse, and cred_v2
6. generate the certificate request using the following command:
sapgenpse get_pse –v –r certreq –p local.pse “CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE” do not enter a PIN (just press enter)
7. copy the contents of certreq to the clipboard
8. browse to http://www.service.sap.com/saprouter-sncadd
9. paste the contents of the clipboard into the form
10. step through form to generate new certificate information
11. copy and paste new certificate data into a file called srcert
11. import the certificate using the following command
./sapgenpse import_own_cert –c srcert –p local.pse
do not enter a PIN (press enter)
12. setup the login using the following command
sapgenpse seclogin –p local.pse
this will create a final file called cred_V2
13. check if the certificate has been loaded correctly by using the following command:
sapgenpse get_my_name –v –n Issuer
14. start the router service
15. delete backup router directory made in step 3 if it is no longer needed
CN and OU information will be different and based on the configuration for your company.
2. stop the router service
3. backup the router folder
4. change to the sap router directory
5. rename or delete these files: certreq, srcert, local.pse, and cred_v2
6. generate the certificate request using the following command:
sapgenpse get_pse –v –r certreq –p local.pse “CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE” do not enter a PIN (just press enter)
7. copy the contents of certreq to the clipboard
8. browse to http://www.service.sap.com/saprouter-sncadd
9. paste the contents of the clipboard into the form
10. step through form to generate new certificate information
11. copy and paste new certificate data into a file called srcert
11. import the certificate using the following command
./sapgenpse import_own_cert –c srcert –p local.pse
do not enter a PIN (press enter)
12. setup the login using the following command
sapgenpse seclogin –p local.pse
this will create a final file called cred_V2
13. check if the certificate has been loaded correctly by using the following command:
sapgenpse get_my_name –v –n Issuer
14. start the router service
15. delete backup router directory made in step 3 if it is no longer needed
CN and OU information will be different and based on the configuration for your company.
Subscribe to:
Posts (Atom)