Skip to Content
Technical Articles

Solution Manager 7.2 SP 08,NW 7.4 Migration Post Steps – X– Java Stack

Solution Manager 7.2 SP 08,NW 7.4 Migration Post Steps – X– Java Stack

After successfully completing java stack migration using SWPM Export Import method which I have explained in previous blogs ,there are few post steps which needs to be performed right after the migration process.

Solution Manager 7.2 SP 08,NW 7.4 Migration Using SWPM – VIII – Export Java Stack

Solution Manager 7.2 SP 08,NW 7.4 Migration Using SWPM – IX– Import Java Stack

Lets continue with post steps in this blog

->First generate the JAVA license (Select HANA DB)  from SAP Support Portal and then start the java stack system

->On Java Server run the below hdbuserstore command

>hdbuserstore SET DEFAULT “<hostname FQDN>:port no” Schema Name <Password>

Let me give few basic understanding about hdbuserstore in this blog.

hdbuserstore is a tool installed along with SAP HANA Client package installation.It is used to store connection information to SAP HANA systems securely on the client so that client applications can connect to SAP HANA without users having to enter this information. It is typically used by scripts connecting to SAP HANA.

The secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. In this way, client applications can connect to SAP HANA without the user having to enter host name or logon credentials.

The secure user store is installed with the SAP HANA client package. After you install the SAP HANA client, the hdbuserstore program is located in one for the following directories:

  • /usr/sap/hdbclient (Linux/UNIX)
  • %SystemDrive%\Program Files\sap\hdbclient (Microsoft Windows)

The secure store runs on all platforms supported by SAP HANA client interfaces and SAP BASIS 7.20 EXT.

To access the secure store using JDBC, there are two connect options: key and virtual Host Namekey is the hdbuserstore key that you use to connect to SAP HANA, while virtual Host Name specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files.

To connect, define the hdbuserstore key using the key connect option. JDBC only supports reading the key and data files for existing keys and using those keys to connect to SAP HANA.

Managing the Secure Store

Connection information stored in the secure store is saved in the secure store file SSFS_HDB.DAT.

For Linux/UNIX systems, the path is defined by <HOME>/.hdb/<COMPUTERNAME> where:

  • HOME is the home directory of the user that uses the logon information.
  • COMPUTERNAME is the computer name.

If the path does not already exist, then the hdbuserstore program creates it.

The secure store’s content is stored in a platform-dependent way. You cannot copy the secure store from one platform to another.

Using Stored Connection Information

When the secure store is accessed in the context of the correct operating system user, you can open it with a user key.

Client How to Connect Using a Stored User Key
SAP HANA HDBSQL In SAP HANA HDBSQL, you specify the key to be used with the -U connection option: hdbsql -U <KEY>
ODBC In ODBC, you specify the user store key with the @ sign in your data source:servernode=@<KEY>
ABAP ABAP uses the key DEFAULT by default.

Command hdbuserstore list provides information about DATA and KEY file as shown below

->Now login to NWA (Netweaver Administrator) of java stack

http://<hostanme>:5XX00/nwa (XX->Instance No)

Reinstall the JAVA license key (Select HANA DB)

->Next add the java system to Hana studio as a tenant database.

->Cross check the LMDB whether new technical java system updated or not, sometimes LMDB doesn’t update the new server in that case we need to manually create new technical system in LMDB

Execute t-code LMDB , navigate to Technical systems->Select Type ABAP or JAVA ->Create

Click Next

Click save

Click Resynchronise technical System from SLD

Click Save and navigate to Infrastructure Preparation in SOLMAN_SETUP

Under Mandatory Configurations Re-execute the Infrastructure Preparation step

I faced one error at step 2.2 Enable Connectivity->Check Java Software Prerequisites

>SOLMAN_SETUP->Infrastructure Preparation->’Check Java Software Prerequisites’ failed with error ‘ISAGENT_MIN_J5 10.5 component is not installed’

Click on log

Error: ISAGENT_MIN_J5 10.5 component is not installed

For above error, implement below note in SAP system

2764798 – ‘Check Java Software Prerequisites’ failed with error ‘ISAGENT_MIN_J5 10.5 component is not installed’

As per the above note , there is a coding error after upgrading to SAP SOLUTION MANAGER 7.2 SPS 08, hence Implement note correction below.

2739682 – Activity ‘Check Java Software Prerequisites’- Implement this note in the respective SAP Solution Manager system and the again cross check step Infrastructure Preparation and execute selected activity, it shows error resolved.

Troubleshooting Information for Running SOLMAN_SETUP in SAP Solution Manager 7.2

->Configure your SAP Solution Manager 7.2 SPS 08 system using SOLMAN_SETUP.

Finally, after completing upgrade of the SAP Solution Manager 7.2 SPS 08 system needs to be configured as described in SAP Note 2227300.

 

 

 

 

 

 

 

 

 

Be the first to leave a comment
You must be Logged on to comment or reply to a post.