MiniWAS 620 installation - Unsolved problems

[Former Member]

Hello everybody,

I need expert advise on some topics. I have purchased recently SAP Mini Web AS 620. After several installations (even formatting hard disk), I have not been able to solve every error I faced on Mini WAS installation. I am

grateful to everyone in this website who has given solutions. Before witting any message when an error shows up, I tried to

solve it myself with other messages already answered, but now I still have two unsolved problems (what else do I have to do):

1.- Business Server Page (BSP) Error

2.- Import ABAP request (MiniWAS examples)

Additional info:

a. Labtop installation

Windows XP home edition SP 2

Please some help will me appreciated.

I have this information, maybe someone can give an idea:

**************************************************************************************************************

1.- Business Server Page (BSP) Error

**************************************************************************************************************

When I run SE80 `with BSP Tutorial_1 I get the following error:

Business Server Page (BSP) ErrorBusiness Server Page (BSP) Error

Was ist passiert?

Call of BSP page terminated due to error.

Note

Following error text processed in system:

BSP Exception: Die URL enthält keine vollständige Domainangabe (camposa statt camposa.dominio.com).

Error Type: Exception

Your SAP Business Server Pages Team

I run F8 on default.htm and my systems first try to conect to WWW. then I cancel this connection, I got an HTTP error,

because the systems tries to connect to:

http://camposa.dominio.com:8080/sap/bc/bsp/sap/tutorial_1/default.htm?sap-client=000&sap-sessioncmd=...

I do not get a window asking for User: BCUSER / Psw: minisap. If I change previous www address an instead of

camposa.dominio.com I write camposa, then I got the dialog asking for user/psw. Later, I got the BSP error.

I defined a MS loopback network. Also defined an entry in system32/host with 10.10.0.10 camposa.dominio.com

I also define parameter icm/host_full_name.

My Instant profile is:

#.***************************************************************************************************************************

***

#.*

*

#.* Instance profile BSP_D00

*

#.*

*

#.* Version = 000002

*

#.* Generated by user = BCUSER

*

#.* Generated on = 04.04.2005 , 15:26:55

*

#.*

*

#.***************************************************************************************************************************

***

SAPSYSTEMNAME = BSP

INSTANCE_NAME = D00

SAPSYSTEM = 00

1. ausschalten alert monitoring

alert/MONI_SEGM_SIZE = 2000000

1. beginn der aenderung (alle Pfade geaendert)

exe/gwrd = .gwrd.exe

exe/dispwork = .dispwork.exe

DIR_EXECUTABLE = .

DIR_PROFILE = .

DIR_GLOBAL = .

DIR_INSTANCE = .

DIR_INSTALL = .

DIR_PERF = .

DIR_TRANS = . rans

DIR_PUT = .put

DIR_HOME = .

DIR_LOGGING = .

DIR_DATA = .

DIR_AUDIT = .

DIR_LIBRARY = .

DIR_PROTOKOLLS = .

FT_DAT =

FT_LOG =

1. ende der aenderung (alle Pfade geaendert)

#rdisp/TRACE = 3

#rdisp/TRACE_COMPS = All

rdisp/wp_no_dia = 2

rdisp/wp_no_btc = 2

rdisp/wp_no_spo = 1

rdisp/wp_no_vb = 1

rdisp/wp_no_enq = 1

PHYS_MEMSIZE = 64

MiniSystem = 1

abap/buffersize = 50000

enque/table_size = 2000

rspo/local_print/method = 2

rsdb/ntab/entrycount = 5000

rsdb/ntab/ftabsize = 3000

rsdb/ntab/sntabsize = 100

rsdb/ntab/irbdsize = 300

rsdb/cua/buffersize = 500

#rsdb/mssql/pn_cache_size= 1000

#rsdb/mssql/tsp_cache_size= 100

rsdb/obj/buffersize = 2048

rsdb/obj/max_objects = 200

rsdb/otr/buffersize_kb = 2048

rsdb/otr/max_objects = 1000

rsts/ccc/cachesize = 1000000

rtbb/buffer_length = 500

rtbb/max_tables = 50

sap/bufdir_entries = 200

zcsa/installed_languages = DE

zcsa/presentation_buffer_area = 350000

zcsa/calendar_area = 300000

zcsa/table_buffer_area = 2000000

zcsa/db_max_buftab = 300

ztta/roll_area = 1000000

ztta/diag_area = 128000

ztta/dynpro_area = 150000

ztta/cua_area = 180000

rdisp/PG_SHM = 100

rdisp/ROLL_SHM = 100

rdisp/autoabaptime = 0

rdisp/bufrefmode = sendoff,exeoff

rdisp/elem_per_queue = 50

rdisp/wp_ca_blk_no = 20

rdisp/appc_ca_blk_no = 20

rdisp/max_wprun_time = 300

#rdisp/start_icman = false

icm/host_name_full = camposa.dominio.com

icm/server_port_0 = PROT=HTTP,PORT=8080

icm/server_port_1 = PROT=SMTP,PORT=8025

icm/server_port_2 = PROT=HTTPS,PORT=8443

icm/HTTP/server_cache_0/max_entries = 1000

icm/HTTP/server_cache_0/max_name_len = 100

icm/HTTP/server_cache_0/max_ufo_entries = 0

icm/HTTP/server_cache_0/ufo_list = FALSE

icm/HTTP/server_cache_0/memory_size_MB = 0

icm/HTTP/server_cache_0/size_MB = 100

icm/min_threads = 5

icm/max_threads = 10

icm/max_conn = 20

mpi/total_size_MB = 10

alert/MONI_SEGM_SIZE = 2000000

auth/new_buffering = 1

transport/systemtype = CUSTOMER

dbs/ada/schema = SAPBSP

My default profile is:

#.***************************************************************************************************************************

***

#.*

*

#.* Default profile DEFAULT

*

#.*

*

#.* Version = 000004

*

#.* Generated by user = BCUSER

*

#.* Generated on = 04.04.2005 , 15:26:55

*

#.*

*

#.***************************************************************************************************************************

***

SAPSYSTEMNAME = BSP

SAPDBHOST = camposa

rdisp/mshost = camposa

rdisp/msserv = sapmsBSP

SAPSYSTEM = 00

rdisp/sna_gateway = camposa

rdisp/sna_gw_service = sapgw00

rdisp/vbname = camposa_BSP_00

rdisp/enqname = camposa_BSP_00

rdisp/btcname = camposa_BSP_00

rdisp/bufrefmode = sendoff,exeoff

login/system_client = 000

ZTTA/DEFTITLE = "SAP ABAP Engine"

I get this information from ICM monitor:

Application Server State

HTTP Application Server Handler

ABAP Server operational = TRUE

J2EE Server configured = FALSE

J2EE HTTP port =

J2EE HTTPS port =

J2EE Server operational = FALSE

Default root access handler = ABAP

URL Prefix Table loaded = TRUE

URL Prefix table

URL Prefix Virtual Host Case Sensitive Part

/sap/ :;

And the ICM Parameters are:

Plugins

icm/plugin_0 = PROT=HTTP,PLG=.httpplugin.dll

icm/plugin_1 = PROT=HTTPS,PLG=.httpplugin.dll

icm/plugin_2 = PROT=SMTP,PLG=.smtpplugin.dll

Services

icm/server_port_0 = PROT=HTTP,PORT=8080

icm/server_port_1 = PROT=SMTP,PORT=8025

icm/server_port_2 = PROT=HTTPS,PORT=8443

Hard limits

icm/max_services = 50

icm/listen_queue_len = 512

icm/req_queue_len = 500

icm/max_conn = 20

icm/max_sockets = 2048

Thread handling

icm/min_threads = 5

icm/max_threads = 10

icm/min_spare_threads = 3

Tracing and statistic

rdisp/TRACE = 1

icm/tracefile = dev_icm

icm/log_level = 0

icm/stat_level = 1

icm/accept_remote_trace_level = 0

Monitoring

icm/ccms_m onitoring = 1

icm/ccms_refresh_rate (sec.) = 30

Timeout handling

icm/keep_alive_timeout (sec.) = 60

icm/conn_timeout (msec.) = 5000

icm/max_timeout_net (msec.) = 2000

icm/min_timeout_mpi (msec.) = 5000

HTTP settings

icm/HTTP/max_request_size_KB = 102400

icm/HTTP/server_cache_0 = PREFIX=/, CACHEDIR=.cache

HTTPS (SSL) settings

icm/HTTPS/verify_client = 1

ssf/name =

ssf/ssfapi_lib =

sec/libsapsecu =

ssl/ssl_lib =

Kontext Quotas

icm/HTTP/context_quota = no quota

icm/HTTPS/context_quota = no quota

icm/SMTP/context_quota = no quota

Memory Pipe settings

mpi/total_size_MB = 10

mpi/buffer_size = 65536

J2EE settings

rdisp/j2ee_start = 0

is/HTTP/default_root_hdl = j2ee

Misc

icm/host_name_full = camposa.dominio.com

icm/cancel_strategy = cancel requests without session (stateless)

is/HTTP/virt_host_0 = :;

is/SMTP/virt_host_0 = :;

Some other information:

Kernel information

Kernel release 620

Compilation NT 5.0 2195 Servic

Sup.Pkg lvl. 1867

ABAP Load 1462

CUA load 15

Mode opt

Rsyn file

Database information

DB client lib. SAPDB 7.3.1.007

DB releases SAP DB 7.3.0, SAP

DBSL version 620.02

DBSL Patch Level 1012

System Information

IP address 10.10.0.10

SAP versions 610, 620

Operating System Windows NT 5.0, Wi

OP release 5.1

Support packages installed:

SAP ABAP and SAP BASIS, both up to SP32. Everything has been generated thru transaction SGEN.

***************************************************************************************************

2.- Immport ABAP request (MiniWAS examples)

***************************************************************************************************

I have configured my TMS and I got this results from check:

***********************************************************************************

BSP Mini SAP Basis System

tp Interface

Host Name camposa

Version 1.80

Transport Directory . rans

Logging On (TPLOG contains 302 entries)

Transport Profile

Path . rans inTP_DOMAIN_BSP.PFL

Profile TP_DOMAIN_BSP.PFL is readable

Version Version 0005 (domain DOMAIN_BSP)

RFC Destination

Destination CALLTP_WindowsNT

tp Path . p.EXE

tp Executable Size: 8.007.743 bytes

RFC Ping Link setup: 1439 msec

tp Call

RFC Link tp was started successfully

tp Version 320.58.28 (14.01.2002 13:00:00)

DB Connect Link to database successful

Offline Call tp started in background

My TPPARAM files contains:

***********************************************************************************

BSP/DBHOST = camposa

BSP/DBNAME = BSP

BSP/IMPDP_BY_EVENT = yes

BSP/R3TRANSPATH = R3trans.exe

BSP/SAPEVTPATH = sapevt.exe

BSP/SYSTEM_PF = C:MiniWASdefault.pfl

BSP/dbtype = ada

ALLLOG = ALOG$(syear)$(yweek)

SYSLOG = SLOG$(syear)$(yweek).$(system)

TRANSDIR = C:MiniWAS rans

My DOMAIN.CFG file has:

***********************************************************************************

camposa

00

TMSADM

DOMAIN_BSP

Transport Domain BSP

BSP

Mini SAP Basis System

BSP

GROUP_BSP

Transport Group BSP

#----

-

---

#Caution !

#This file was generated by the Transport Management System.

#Do not change this file using a text editor.

#If this file was destroyed, it can be regenerated in the TMS.

#To do this, log on to the domain controller (system BSP) and call

#Transaction STMS. In the System Overview, you can distribute the TMS

#configuration. This regenerates the file.

#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration

#----

-

---

Also, my TP_DOMAIN_BSP file has:

***********************************************************************************

#TMS:0005:DOMAIN_BSP

#A

#

#----

-

---

#Caution !

#This file was generated by the Transport Management System.

#Do not change this file using a text editor.

#For further information please see the online documentation of

#transaction STMS.

#If this file was destroyed, it can be regenerated in the TMS.

#To do this, log on to the domain controller (system BSP) and call

#Transaction STMS. In the System Overview, you can distribute the TMS

#configuration. This regenerates the file.

#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration

#----

-

---

#

#

ALLLOG = ALOG$(syear)$(yweek)

SYSLOG = SLOG$(syear)$(yweek).$(system)

TRANSDIR = C:MiniWAS rans

#

BSP/CTC = 0

BSP/DBHOST = camposa

BSP/DBNAME = BSP

BSP/DBTYPE = ada

BSP/IMPDP_BY_EVENT = yes

BSP/NBUFFORM = 1

BSP/R3TRANSPATH = R3trans.exe

BSP/SAPEVTPATH = sapevt.exe

BSP/SYSTEM_PF = C:MiniWASdefault.pfl

BSP/TP_VERSION = 281

#

VIR/CTC = 0

VIR/DUMMY = 1

VIR/NBUFFORM = 1

VIR/TP_VERSION = 266

I am able to add to buffer request, but every time I try to import, the request seems to 'hang' and keeps been on status

'running import'.

If I run Cmd -> TP TST 'request' BSP, then I got and error '.... E-TPSETTINGS COULD NOT BE OPENED .... error in transportprofil (param missing, unknown ...)...'

I am really lost, anyone has idea what is going wrong?

Best regards and thanks in advance,

Arturo Campos

[Former Member]

Hi Arturo,

With regards to problem 2.

I did a search for any notes with the error "E-TPSETTINGS COULD NOT BE OPENED" and found note 481910:

Symptom

The tp program is called in the command field, however, the path for the transport profile has not been specified with pf=....

The following error message is displayed:

E-TPSETTINGS could not be opened.

Other terms

TPPARAM

Reason and Prerequisites

The function causing the tp program to automatically look for a TPPARAM transport profile has been eliminated.

As of Release 4.5, transports are mainly controlled via the STMS transaction. This transaction writes a transport profile named 'domain name'.PFL. To avoid errors, the transports in the command field must use the same transport profile. Therefore, an automatic search for a TPPARAM file is a potential error source that had to be eliminated.

Solution

Always specify the correct transport profile during the tp call in the command field by setting the pf='transport profile' option.

Instead of using TP you can also use transaction STMS. For more information have a look at : http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a8197acc11d1899e0000e829fbbd/frameset.htm

You will need to look at: "Adding a Change Request to the Import Queue" and then "Starting the Import for Single Requests"

[Former Member]

For the MiniWAS it's slightly different since the initial configuration is not done upon install, the weblog I listed there will get you over some of the initial install pieces that need to be done.

[Former Member]

Thanks for such quick reply.

I will post BSP problem in the right place. I took a look on that link. I guess I need to update Kernel version. My system actually is on SP 32.

I'll tell how things go.

Best regards.

Arturo Campos

[Former Member]

The TP that came with was an old one so most likely it will be a kernel update oh and be sure you set the directory share on C:\MiniWAS to "sampmnt"

[Former Member]

I would suggest you take a look at this weblog for your TP problems. /people/sap.user72/blog/2004/12/08/mini-me-of-was-620-the-saga-continues

As for the BSP problem, I would suggest you look in the BSP forum for more details.

If I understand your problem correctly, the error comes when you don't use the domain because BSP's require the Full Qualified Domain Name you can search the BSP forum FQDN for info on how do to that.