Skip to Content

Continued from my last blog, Caboodle – Part 1 – The NSP 7.02 Install

Here, I perform the following post installation tasks, that put me in good stead for a comfortable NSP environment. Check back here occasionally, as I add to it.

  • Logical System
  • License
  • Profiles
  • Transport System
  • HTTPS & SapCrypto
  • DB Log Overwrite

Logical System

Access the transaction SALE: IDoc Interface / Application Link Enabling (ALE) → Basic Settings → Logical systems → Define Logical System

If prompted for a Workbench Request, simply create one, then use it.

 

More details can be found here, The Full Monty – Part 2 – Logical System & Virtual Machine, a quarter of the way down.

License

The current temporary license is valid for three months, so there is no need to perform this step. Nonetheless, if you wish, use the instructions here, The Full Monty – Part 3 – License & Profiles.
 

System Profiles

Unlike my previous blog, I decided to only add three Profile Parameters.

  • icm/host_name_full = vm.gingle.com
  • login/create_sso2_ticket = 2
  • login/accept_sso2_ticket = 1

Follow my previous instructions here, The Full Monty – Part 3 – License & Profiles. Remember, this is a new NSP 7.02 system, so some of the errors encountered in “The Full Monty” have been fixed or changed to warnings.

Transport System

I hoped the new NSP, would come configured for this, alas, it is not.

I followed my own notes from The Full Monty – Part 4 – Transport System. However there are some small differences. You may wish to follow my old and new notes, simultaneously.

The current TMS TRANSDIR & DBHOST point to a slightly different host. It does not matter.

I deleted the two TMS ABAP RFC Connections in SM59. New SM59 TMS RFC ABAP Connections will be created automatically.

I updated the TMS conguration with my new FQDN Host values. See below.

 

 

Upon “Saving”, got an error, which I ignored for now.

 

Now to test.

STMS->System Overview->Select the NSP system->SAP System->Check->Connection Test F5

Returned, “Connect to system NSP (host vm) OK”

Then 

STMS->System Overview->Select the NSP system->SAP System->Check->Transport Tool

No surprise to see my old problem under the “tp Call”

 

See the fix, half way down the page, here The Full Monty – Part 4 – Transport System. Search for “Do this, and be VERY CAREFUL”.

Another

STMS->System Overview->Select the NSP system->SAP System->Check->Transport Tool

all was sweet

I finally performed the Configuration Update.

STMS->System Overview->Select the NSP system->SAP System->Update Configuration

and successfully received the “Configuration for system NSP updated” message.

HTTPS & SAPCrypto

Like my previous “The Full Monty” blog, I followed this blog Setup HTTPS (SSL) for the Sneak Preview SAP NetWeaver 04 ABAP Edition on Windows, by Gregor Wolf.

FYI, the NSP installation, has a directory “C:usrsapNSPDVEBMGS00sec”. In which there are two files, “ticket”, and “SAPSYS.pse”.

When I performed Gregor Wolf’s blog, there are some differences I found, which I have pointed out below, under his “Section” headings.

His Section “Prerequisites”

Firstly, where you get it. Look at the four highlighted links

 

Then after navigating through, I chose the 64bit CAR for windows

 

His Section “Unpack and install SAP Cryptolib”

I saved and copied the file “90000113.CAR”, to a VM directory, “c:sapcrypto”.

I also copied “sapcar.exe” from “C:usrsapNSPSYSexeucNTAMD64” to the VM directory, “c:sapcrypto”.

I then unpacked the CAR file, with the command

c:sapcryptosapcar.exe -xvf C:sapcrypto90000113.car

resulting in with the following. The files I used are in the “nt-x86_64” directory.

 

I did not perform his last line, the “copy *” command. I only copied the “C:sapcrypto
t-x86_64sapcrypto.dll”, and the “C:sapcrypto
t-x86_64sapgenpse.exe” to “C:usrsapNSPDVEBMGS00sec”.

 

His Section “Setup”

There are a few issues here. I previously noted them in more depth at The Full Monty – Part 5 – HTTPS & Sapcrypto.

Firstly, I used RZ10 to modify my SAP Instance Profile Parameters accordingly.

I used “icm/server_port_2” to retain the “SMTP” Service. Using “icm/server_port_1” will remove it.

I had to add “ssl/ssl_lib”, in the Instance Profile, and set the value to “c:usrsapNSPDVEBMGS00secsapcrypto.dll”. I received a “Parameter name is not known” message. Nonetheless, I saved, activated the profile.

Here is my Instance Profile after all the changes.

 

Later, I also had to add “rdisp/workdir” with the value “c:usrsapNSPDVEBMGS00work”, because without it, I was getting an error when displaying an error log. It turns out, without this parameter the “workdir” is built using “\vmsaploc” and looked like this “\vmsaplocNSPDVEBMGS00work” .

 

His Section “Create Certificate”

This section is pretty much ok. When he references certain functionality, you will have to hunt around for the appropriate button or menu. Help is here. See highlights on screenshot.

 

No need to enter or change a country.

Certs to download can now be found at

Maintenance & Services->SAP Trust Center Service->Download Area->Root Certificates

Add these certificates to the “Trusted Root Certification Authorities” store.

 

His sections Start SSL Server” and “Test”

All’s ok here.

 

His section “Start BSP Application which needs HTTPS”

Before starting the BSP application, I had to start the BSP ICF Services. Transaction SICF. Service Name is “BSP”.

I activated both BSP nodes under “public”, and “bc”. Choose the “Yes” button on the right, with the icon, to activate sub nodes too.

In SE80, double click the “HTMLB_Samples”, on the left hand side, to get it loaded on the right hand side. Then you can use F8 to execute.

Finally, when running “HTMLB_Samples”, my browser did pop up, but I still got the certificate warning, so I simply followed the steps I wrote down, at the end of my blog The Full Monty – Part 5 – HTTPS & Sapcrypto. That fixed it, and now the browser open straight into the BSP application.

DB Log Overwrite

I cannot help remembering, at some time in the past, I was unable to start an NSP due to the DB log being maxed out. So now, I load the DB Manager, and change the log settings to “overwrite”.

I installed the Database Manager “DBM76”, which can be found in the the “MAXDBTOOLS” directory from the NSP download.

Using the user “control”, and the global password I gave during installation of the NSP. I started the DBM, and added the NSP DB, connected to it, and started it up.

I navigated to the “Log Settings …” and changed the setting to “Overwrite” mode. See my before and after screen shots below.

 

 

That’s covers it all for now.

Continue to my next blog Caboodle – Part 3 – The BOBJ4 Install

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Damandeep Thakur
    Hi,
    When I save, as per section Transport systems, I get error:
    “RFC communications error with system/destination TMSADM@NSP.DOMAIN_NSP
    RFC error when sending logon data.”.

    FYI: I didnot set loopback adapter before installation. Is this the issue?

    Please help to resolve.

    Regards,
    Daman

    (0) 

Leave a Reply