on 2022 Nov 10 6:00 AM
Dear Experts ,
Wishing another successful day for you all ,
Recently we have experienced below error while going to initiation of Sap Customer Checkout manager in HANA flatform .
SAP DBTech JDBC: Cannot connect to jdbc:sap://127.0.0.1:30041 [Cannot connect to host /127.0.0.1:30041 [java.io.IOException: The remote computer refused the network connection: 127.0.0.1:30041], -813.].
So when google the issue we got the SAP Note : 2501339 - Error: "SAP DBTech JDBC: Cannot connect to jdbc..." occurs when connecting tenant DB by using JDBC driver
and did the mentioned resolution as below ,
You can determine the ports used by a particular tenant database by querying the M_SERVICES system view, either from the tenant database itself or from the system database.
From the tenant database:
SELECT SERVICE_NAME, PORT, SQL_PORT, (PORT + 2) HTTP_PORT FROM SYS.M_SERVICES WHERE ((SERVICE_NAME='indexserver' and COORDINATOR_TYPE= 'MASTER') or (SERVICE_NAME='xsengine'))
From the system database: Exchange the <DBNAME> to your tenant DB SID in the following SQL.
SELECT DATABASE_NAME, SERVICE_NAME, PORT, SQL_PORT, (PORT + 2) HTTP_PORT FROM SYS_DATABASES.M_SERVICES WHERE DATABASE_NAME='<DBNAME>' and ((SERVICE_NAME='indexserver' and COORDINATOR_TYPE= 'MASTER') or (SERVICE_NAME='xsengine'))<br>
We got the result when run the first sql script as below,
SERVICE_NAME; PORT; SQL_PORT; HTTP_PORT
indexserver ; 30040; 30041; 30042
And as advised 2nd point in the resolution try to config using the SQL_PORT 30041 but giving the error as mention in the begining of this query . other two port numbers also tried but not succeeded.
So could anyone advise on this matter to move forward . Really appreciated if possible .
SAP Business one HANA version 10 FP2102 and Sap Customer Checkout Manager 2.0 FP14PL00
Thanks in advance .
Best Regards,
Tharindu Wijesinghe.
Request clarification before answering.
Dear Joerg ,
Really thankful your support on this so far and finally we have identified the real reason for above errors . It's because for a research purpose we had used sapmachine-jdk-19.0.1_windows-x64 folder in the java directory instead of using sapmachine-jdk-11.0.11_windows-x64 . So after been tried every thing just downgraded the jdk and checked . Then only the problem got resolved . So we learned from that the latest version of SAP machine jdk shall not compatible with this situation . So thanks again for your assistance given on the above matter till now . Here after the initiation process been done with out any issue so as the main login after initiation .
Have a great day ahead .
Thanks and Best Regards,
Tharindu Wijesinghe .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello tharindu
I would recommend not using the SQL port of the tenant database, but going through the nameserver instead. That means using port 30013 and specifying the tenant database name as part of the connection string. Like so:
Note that our tenant database is called CCOM, so we actually keep it separate from any B1 tenant databases. You can easily create a new tenant database for CCOM using:
CREATE DATABASE CCOM SYSTEM USER PASSWORD "<complex-password>";
Within that tenant database, using the SYSTEM user, we then create one user for each CCOM tenant, including the master tenant. Each user created automatically creates a schema with the same name, and that setup also creates complete user rights isolation between tenants. For example, within the tenant database, create a user like this:
CREATE USER CCOM_MASTER_FP14 PASSWORD "<another-complex-password>";
ALTER USER CCOM_MASTER_FP14 DISABLE PASSWORD LIFETIME;
Then just set up your CCOM using the JDBC connection string, user, schema and password similar to the screenshot above.
Hope this helps.
Best regards,
Joerg.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Joerg,
Greetings for another great day...!
As you advised we have setup the test environment and did the initiation , Kindly find below screen shots for your reference .
And the initiation was successful . ASCM schema also been created with in that tenant as follow,
But Here after try to login the Checkout manager for the first time it giving below error ,
We afriad that cannot figure out what will be the issue here . So if you can advise to sort this matter as well it's really appreciated . log-30013.txt
Thanks and Best Regards,
Tharindu Wijesinghe.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello tharindu
Try to enable the browser dev tools to see more details about your login request failing.
I also find it strange that the labels on the login form are not loading the localized strings (it shouldn't say "TITLE_LOGIN_FORM"). That usually points to an incomplete/incorrect deployment of the .war file itself. Maybe try to redeploy the war file. Also look for errors in the catalina log file when doing that.
Best regards,
Joerg.
Dear Joerg,
It's well noted and Thanks for your detail explanation.
Actually this is a test environment which created for testing before go to the live environment . we are also used two different tomcat instances to setup the same so as in the below screen shot the files been created when setup initiation in two different folders (SAPASCMTEST and SAPHSCMTEST)
We shall try again to create new separate databases in our scenario using advise been given below and initiate the setup again.
{Also, you didn't pay attention to the JDBC connection URL I provided. Look again and identify the "databaseName=CCOM" parameter which you have not provided in your case. Schema and database are separate concepts. If your B1 tenant database is called NDB, you can perfectly use "databaseName=NDB" in the connection URL, B1ADMIN as the user with the corresponding password, and any schema name that is not currently in use. }
Shall let you know the update accordingly . Thanks for the continues support as always .
Best Regards,
Tharindu Wjesinghe.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello tharindu ,
I don't think you can actually set up two separate instances of CCOM on the same Tomcat instance, just by renaming ccos.war to different names. The reason is that Tomcat itself provides the Java Runtime environment and that in turn provides the config file path (/SAP/Customer Checkout Server/ by default). That means the two instances will both try to write to the same config and log directories, which will most certainly fail.
We are currently running four different CCOM versions on the same (SUSE Linux 15.2) server, using four separate Tomcat instances. Two of those are configured using SQL Server, and the other two are configured using SAP HANA.
Each has their own config and log directory set up from the service initialization script. For example, FP14 points to /SAP/ccom-fp14, as configured here:
Of course, each of the instances runs on a different port:
And then, the whole server is actually set up behind an nginx reverse proxy installation, that does the actual SSL termination and routes each request to the corresponding Tomcat instance based simply on hostname identification.
While most of this setup is used for testing, we do have a couple of live customers on this installation with reasonable receipt volumes. The RAM consumed altogether is 8 to 10 GB, with four CPU cores the average CPU consumption is negligible.
With regards to the database creation error, you need to execute that command from SYSTEMDB, you can't do it from NDB or HDB as you might have set up B1.
Also, you didn't pay attention to the JDBC connection URL I provided. Look again and identify the "databaseName=CCOM" parameter which you have not provided in your case. Schema and database are separate concepts. If your B1 tenant database is called NDB, you can perfectly use "databaseName=NDB" in the connection URL, B1ADMIN as the user with the corresponding password, and any schema name that is not currently in use.
Hope this helps.
Best regards,
Joerg.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Joerg ,
Really appreciated your quick respond and for the valuable information been shared .
In our scenario we need to have multiple customer checkout manager in the same server so we going to initiate two instance first . When going to config first Checkout manager this happens , we have seperate apachi setup and seperate ccos.war file been copied after renaming as hasm.war and ascm.war .
As mention we have tried to create new data base using given script but came up with error as below,
Could not execute 'CREATE DATABASE HSCM SYSTEM USER PASSWORD "<Abc@123>"'
SAP DBTech JDBC: [7]: feature not supported: Create database command on SYSTEMDB only
But anyway we tried to config using 30013 port but giving below Authentication error,
So then we restarted the server and services. Here after again check whether connecting by via 30041 this time without error the initiation get succeeded.
Then the login screen came and going to log the below error displaying , No tenant been created because still in the initiation level .
The error log has also been attached here for your kind reference and Could you advise what might be the reason for this and did we done any wrong here .
Best Regards,
Tharindu Wijesinghe .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
20 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.