Showing posts with label Solution Manager- Installation on Windows / Oracle. Show all posts
Showing posts with label Solution Manager- Installation on Windows / Oracle. Show all posts

Sunday, November 18, 2007

Changing the saplogon image

This document briefly describes how to customize the image that is displayed on the right-hand side of the session manager screen.

Preparing the Image

The image can be in GIF or JPEG format. (And possibly others.) Use an image that is less than 20 KByte in size because the image size affects the loading time of the session manager screen. An image size of 300 pixels wide by 250 pixels high seems to work well. By default the GUI will scale the image to cover the available space on the session manager screen.

Define the MIME Types

The MIME type for the image format you are going to use needs to be defined in SAP. This only has to be done once for each image format.

  • Execute transaction SMW0.
  • Select Binary data for WebRFC applications and click the find button.
  • On the next screen enter development class SWF and click the execute button.
  • This takes you to the SAP Web Repository: Object Display screen. Go to Settings >> Maintain MIME types.
  • In this screen, create new entries for the image formats you want to use if they do not already exist.

Type

Extension

image/gif

*.gif

image/jpeg

*.jpg, *.jpeg

Create an Object for the new Image

The image that will be used will have to be stored in the database. You can simply replace the SAP standard image and be done with it, but this is not recommended. The image should be stored as a new object in the database.

  • In the SMW0 transaction, go to the SAP Web Repository: Object Display screen as described above.
  • Click the create button.
  • Enter the object name and description, CUSTOM_LOGON_IMAGE for example, and click the import button.
  • Select the image file you want to use and click Transfer.
  • Confirm the pop-up about having to use an SAP development class.
  • In the next screen enter development class SWF. This is the same development class as the SAP standard image stored in the RIPPLE object. Click the save button and confirm the warning about the original system being set to SAP.
  • Depending on the configuration of your system you may be asked for a transport number.

Should you ever want to replace the image you can just upload the new image into the same object.

  • In the SAP Web Repository: Object Display screen select the object with the image you want to replace and click the import button.
  • Confirm the pop-up that you really want to replace the old object.
  • Select the image file you want to use and click Transfer.
Configure the System to use the Customized Image

The last step is to configure the system to use the customized image. This only has to be done if you want to use an image from another object. If you changed the image by uploading it into the same object you do not have to do this.

  • Execute transaction SM30.
  • Enter SSM_CUST as the table/view and click Maintain.
  • Create a new entry named START_IMAGE. Enter the name of the object holding the image created earlier.

The change is in effect immediately after you save it. Do System >> Create session to see the results.

Questions?

Q. Can I have a different image in each client?
A. No, as far as I know the change is client independent.

Q. I did everything they way you said but I do not see the image!
A. Check the following:

  • Is HIDE_START_IMAGE set to YES in SSM_CUST?
  • Is Do not display image checked in Session manager >> Extras >> Settings?
  • Is the divider between the menu tree and the image all the way over to the right?

Q. Where do I find more information?
A. When you log on to SAP with ‘elevated privileges’ there is an extra menu option Extras >> Administration information on the session manager screen. This explains in very generic this and some other customization that can be done. You can use this as a starting point for investigating the issue in OSS and on the Web.

SLD Configuration

SLD configuration for J2EE

Proceed as follows:
1. Start the J2EE Engine if you have not already done so.
2. Start the engine administrator console using the path :\usr\sap\\CI\j2ee\admin\go.bat.
3. Choose Connect and log on to the J2EE Engine. You need administrator rights for the login process.
4. After login, choose the Cluster tab on the left, expand the node Server, Services, and choose SLD Data Supplier.
5. Choose CIM Client Generation Settings and specify the necessary HTTP connection parameters to establish a connection to the SLD.

Example I'm using Solution Manager as my SLD server also.

host solman.sapecc.com
port 50000 or what ever is your port.
user SLDDSUSER
password **********

Note: SLDDSUSER should have LcrInstanceWriterAll role assigned

6. Save the data by pressing the Save button
7. Choose the CIM Client Test button to check the CIM client connectivity.
8. If the test was successful, you can close the J2EE Engine Administrator Console. Otherwise correct your connection parameters.
Do the same for http connection.

Assign the application role to user groups. This is button to the right. Then tigger the data transfer

Verification of data transfer:
Go to your SLD server example: http:solman.sapecc.com/sld
Home > Technical System
You should see the current time stamp for JAVA system

Configuration for ABAP System

Go to transaction RZ70
Select Automatic RFC Destination
Host: Your SLD sever (I put solman here, since that is my SLD Server.)
Service : sapgw00 (if your instance is 00)

Save the setting using button. Then schedule the job using .

If you have error message make sure that your RFC is configured properly.
Check for RFC SLD_UC for unicode system using transaction SM59. Test the connection and it should not error out.

Verify the data transfer : Go to your SLD server in my case http:solman.sapecc.com/sld
Home > Technical System
You should see the current time stamp for ABAP system

Install the SAP Solution Manager

Install the SAP Solution Manager

Run transaction SAINT in client 000 and use the menu path shown to transfer the Add-On package from your PC to the application server 1. Run transaction SAINT in client 000 and use the menu path shown to transfer the Add-On package from your PC to the application server

To install the Add-On: In the main SAINT screen, select the Add-On files "OCS package".
To begin the import, choose solution_manager_1 then solution_manager_2 .
The status bar shows the different import phases. In most cases the installation takes 15-20 minutes.

Once successfully installed you will get this screen
solution_manager_3

Create Role

  1. Run PFCG
  2. Copy SAP_SV_Solution_Manager to Z_SV_Solution_Manager
  3. Make sure you generate the newly created role

Create RFC User

  1. Run SU01
  2. create user solman_rfc. Make sure that the user is system user
  3. Assign the user profile D_SOLMAN_RFC
  4. Save and exit.

Create RFC

  1. Run SM59
  2. Choose create
  3. Enter connection type '3' and maintain the description. Then press return. The fields for the target host details The fields for the target host details4. Test the connection by choosing Remote logon. If the connection succeeds, a logon screen is not displayed.
  4. Test the connection by choosing Remote logon. If the connection succeeds, a logon screen is not displayed.

Solution Manager- Setup Time Zone / Local Printer

Set up Time Zone.

This activity sets up the appropriate SAP instance time zone, which is aligned to the server’s time zone.

  • Access the activity using the following option

Transaction Code

STZAC

  • On the Change View “Customizing time zones”: Details screen, make the following entries:

Field

User Action or Values

System Time Zone

PST

User’s Default Time Zone

PST

Time zones active

Selected

  • Choose Save.
Setup Local Printer
  • In the Command field, enter transaction code SPAD and choose Enter.
  • On the Spool Administration: Initial screen, in the Output devices field, enter LOCL and choose Enter.
  • On the Spool Administration: Output Device (Create) screen, on the Device/Attributes tab, make the following entries:

    Field

    Value

    Device Type

    SWIN: Windows printing via SAPlpd

    Device Class

    Standard Printer

    Location

    Default printer connected to frontend (type SAPWIN)

  • Choose the Access Method tab.
  • Make the following entries:

    Field

    Value

    Host Spool Access Method

    F: Printing on Front End Computer

    Host printer

    __DEFAULT

  • Choose Save
  • Choose Back.

Solution Manager- Profile Param

Profile Parameter setup
After installation, the profile parameters are only present at operating system level. To use the profile administration of the SAP system, the profiles must be imported into the database. During this import, the system performs a consistency check and a check of the way in which the parameters interact.
Changes to profile parameters can then be performed in the SAP system. These changes are then stored in the database, and written back to file level. The changes only take effect when they are read by the system; that is, at a restart of the system.

You perform the administration and maintenance of profiles in transaction RZ10.

  • In the first step, you import the profiles into the database by choosing Utilities > Import Profiles > Of active servers.

Changes to instance profiles To change the values of individual parameters, select the corresponding default profile and change this in Extended Maintenance.
After making your changes, choose Copy and then Save. Then, in the list view, choose Copy and then Back. Save the new version of the profile and confirm the activation of the profile in the dialog box.

Solution Manager- Applying Patches

Before you begin the install you will need to download the patches and save them as an .xlm file. This file contains all the patches that will need to be installed. You can use the Java Support Package Manager (JSPM) to apply the patches.

  1. Move all the download patches to /usr/trans/EPS/in

*Note: you will not need to unpack the files.

  1. Start the Java Support Package Manager (JSPM) to apply the latest patches by entering /usr/sap/SED/D*/j2ee/JSPM/go.sh
  2. Follow the instructions and start the patch install
  3. When the JSPM is updated you might have to restart the install using JSPM
  4. If the kernel patches are installed make sure to run root.sh
  5. Apply the ABAP Patches
  6. Logon to the 000 client
  7. Create a user ID using sap*

*Note: you can’t install patches using sap*

  • Update the SPAM
  • Load all the patches and start importing the patches from the top

Solution Manager- Installation on Windows / Oracle

Binary Download Preparation : Download the Binaries form here
Download >> Installations and Upgrades >> My Company’s Application Components >> SAP solution Manager >> SAP Solution Manager 4.0 >> Installation and Upgrade >>Windows Server >>Oracle >>Downloads tab

Once the download is done. Unzip all the necessary files. I generally make folder with sensible name than using the default 510...

Hardware and Software Requirements: Make sure you install Windows 2003 Server Edition as it is a requirement for Netweaver 2004s.

Follow SAP's guidelines for file system layout. Since my install is a Sandbox environment. I made two additional file system other than C: Drive. One drive will be used to put the oracle mirror logs files, or else if you choose default install, SAP puts the mirror logs on C: Drive. I made the data drive 70 GB.

Make sure you patch OS and apply the latest support packs.

Install Java SDK: Download JAVA SDK and Cryptographic file from here.
Once you install Java SDK, make sure that the path variable is set correctly. This should include %JAVA_HOME%\bin; at the begining of the PATH string. You can verify this by typing command java -version. This should show the version you have installed.

Installation of SAP

Start the install as a root directory: Logon to the host as user administrator
Go to Installation_Master DVD and run sapinst.
Select central instance. Complete the installtion.