LANSA Installation on Windows server

[kno_dk]

Hi.

I am going to setup my first LANSA installation in a pure windows enviroment. I have a SQL database (None LANSA ERP-system) on a windows server, and I am going to deploy a new LANSA VL-WEB application into this enviroment.

I am planning to have a seperate windows server running the WEB- server and then connect to the SQL server via ODBC.

Is that the right setup?
What lansa component do I have to install on these 2 servers?
Where do I deploy my VL-WEB applications? on the Web-server or on the SQL server?
Should I have 2 partitions in this setup? one for test and one for production.
How to I deploy the application the first time? which deploymnet package do you recommend?
How to I deploy changes to application afterwards? which deploymnet package do you recommend?
Do you deploy EPC's in deployment packages or do you install them manually?
Where do I have my LANSA license?

I hope you would share your do's and don'ts regarding all this deployment stuff.

/Klaus

[Dino]

Hi Klaus

Deploy works faster with one machine having both versus split in two, but maximum fast is not always the main driver

Lansa license goes in the application server not the sql server

Two partitions, I would do two deployments

If you installed the sql server, the deployment can install the rest.

Review the deployment guide and tutorial, later deployments are releases or versions to the same deployment

Epcs go with the deployment

Experiment a bit to practice, you can always uninstall and redeploy. Deploy a one page with a server module

[kno_dk]

Hi.

Should I have the user created befor the installation and checked that it is able to use the ODBC?

"two partitions, I would do two deployments " - do you mean install it 2 times or create the deployment 2 times each with different Partitions in the settings ?

[Dino]

You can create the user, odbc connection and authorize the user to it. There is another post about using the same user in two servers if you go that route.

And the deployment tool is ran from inside the partition. If you have two partitions, you will have two deployments.

I have not tried installing the same package twice in the same machine

[kno_dk]

It fails when it trys to create the ODBC.

What do you choose when the installation as for DBMS type (I have MSSQL, SQLANYWHERE, NONE, ORACLEODBC, MYSQL and SQLAZURE)

I have selected MSSQL and the it prompts for Data Sourcename, server,database,user and password and I have to choose to create Local databaase.

When i the get to the installation the it fails with "error failed to connect to "MSSQL" server XXX or the databsase LANSADB DREIVER = "

and nothing more.

Is it trying to create a local database for the internal LANSA DB or is it trying to connect to the SQL server where the ERP SQL db are to install the internal LANSA DB??

[Dino]

Check here

viewtopic.php?f=3&t=2716&p=8158&hilit=Karl#p8178

[kno_dk]

Hi

I think I have solved my problem.

On the SQL server I have checked if the DBA has disabled SQL Server Browser Service. If this service is stopped it does not broadcast its availability on the network.

And it was disabled. I think if it is disabled the installation of the deployment is not able to create the ODBC even if it should be able if the correct name of the SQL server was typed in.

I will continue my test.

/Klaus

[kno_dk]

Hi.

I have tested a bit more.

when I try to install lansa on the Application server I get this errors on the server, it gives me the same error if I try to point the ODBC to the Database server or the SQL on the Application server:

hu Aug 22 12:47:06 2024
Version 15.0.0 Build 4403 Windows Server Server Standard (Full Installation) Edition Release 1809 (10.0.0.0 Build 17763) Windows Full UI
Message : [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid object name 'LX_DTA.LX_F96'.
SQL Error Code : 208
Routine : X_DBI_Allocate_SQLDA
Job Number: OS User : Administrator
GUSR=QOTHPRDOWN TPTH=c:\windows\temp PROC=*INSTALL QUET=Y MODE=B UPGD=NO UPCD=DF5B3268-45B5-4746-871B-6B39ED6ECADE PART=C5W LANG=DAN DBUT=MSSQLS DBII=LANSA PSLU=C5TEST PSTC=NO ASTC=NO APPL=C5TEST PSTY=*OTHER UPCF=PROMPT UPDF=PROMPT UPSI=YES XENV=X_HASH_SIGN_CHAR=Æ RNDR=X SUDB=N INST=MSI DEVF=256 DBCL=1 DBTC=N DBCF=CT_INTEGRATED_LOGON:N DBUS=PCXUSER
ROOT=C:\Program Files (x86)\fourcom\test af c5\X_Win95
==============================================================================
Thu Aug 22 12:47:06 2024
Version 15.0.0 Build 4403 Windows Server Server Standard (Full Installation) EditionMessage : (0183) - Fatal and unexpected SQL error when attempting to use the named SQL table.
SQL Table : LX_F96
SQL Error Code : 208
Routine : c:\l4wbuild\v15\patches\work\x_win95\x_lansa\src\x_fun5.c
Job Number: OS User : Administrator
==============================================================================
Thu Aug 22 12:47:07 2024
Version 15.0.0 Build 4403 Windows Server Server Standard (Full Installation) EditionMessage : (0183) - Fatal and unexpected SQL error when attempting to use the named SQL table.
SQL Table : LX_F96
SQL Error Code : -9997
Routine : c:\l4wbuild\v15\L4W15000\work\x_win95\x_lansa\src\x_xql8.c
Job Number: OS User : Administrator

I have looked a trace in windows and on the SQL server but I gives me no info regarding what is wrong. I have tested with the same user in the ODBC and the test was OK.

Does anybody have experies in deploy a VL-Web application to a windows server enviroment whichcan give some hints?

/Klaus