Connection with UD CONNECT
DynaSys is a MSSQL tool, BW WBP was on an AIX server (now AWS). No ODBC driver exists between BW and MSSQL server in Linux / AIX.
This problem was solved setting an UD connect connection
The database name is DYNASYS_ITF
User ID for DynaSys connection is dynasys_itf_bw / Password (see with Etienne Ribet)
(...dynasys_itf_hanasdi in Hana)
Main servers:
DynaSys Development server => dynasysdev1.eua.solvay.com => connected to WBD
DynaSys Testing server => dynasystst1.eua.solvay.com => connected to WBQ
DynaSys Testing server => dynasystst1.eua.solvay.com => connected to WBV
DynaSys Production server => wdcdyap21\dy_dbprd => connected to WBP (will be changed to dynasysprd1.eua.solvay.com the July 1st, 2022)
Previous one (update given by Marc Coste during DynaSys M2C project 10634)
Dynasys is a MSSQL tool, BW WBP is on an AIX server. No ODBC driver exists between BW and MSSQL server in Linux / AIX.
This problem was solved setting an UD connect connection
User ID for Dynasys connection is Dynasys_Interface / Password : 791hB6zi8Rk1DBSV3uNG (Prod/Tst/Dev)
Main servers:
DynaSys Sandbox server => WDCDYWP21\DY_DBSDX => not connected to BW (no DataHub on the Sandbox)
DynaSys Development server => wdcslvbd31\slv1_dbdev => connected to WBD
DynaSys Testing server => wdcslvbt31\slv1_dbtst => connected to WBQ
DynaSys Testing server => wdcslvbt31\slv1_dbtst => connected to WBV
DynaSys Production server => wdcdyap21\dy_dbprd => connected to WBP
Previous one (update given by Abdelmôti 2019/03/22)
- Dynasys Production server: WDCCLSLVBP01\SLV1_DBPRD => connected to WBP
- Dynasys Testing server: WDCCLSLVBV01\SLV1_DBTST => connected to WBQ
- Dynasys Testing server: WDCCLSLVBV01\SLV1_DBTST => connected to WBV
- Dynasys Development server: WDCSLVBD11\SLV1_DBDEV => connected to WBD
Important:
- Adagio Team/InfoSys is in charge of UD Connect connexions. Admin Change to be created by Saints Zhang / Francesco Dilillo for any change or issue.
- Wintel Operations is in charge of DynaSys servers (Contact Abdelmôti KHABABA)
Known Issues
Field XXX is not a member of XXX
This is a known problem that has already been encountered. Some explanation in the following sapnote: https://launchpad.support.sap.com/#/notes/1007409
This is linked to the datasource structure being cached in J2EE layer when using preview functionnality.
Solution: ask cache clearance
| BW System | BW System Description | Java Portal |
|---|---|---|
| WBP | BW Production | BPJ |
| WBV | BW Pre-Production | BVJ |
| WBQ | BW Quality | BQJ |
| WBD | BW Development | BDJ |
| WB1 | BW Sand Box | B1J |
For WB1/WBD/WBQ/WBV, email directly Adagio team
For WBP, ask Saints Zhang to create a Service Request to InfoSys
with following information :
Title : Need to clear JCO metadata caches on BPJ - Tuesday 23th of February - Between 10am and 12pm
Mail :
"We are about to move BW evolutions on WBP.
We need you to clear JCO metadata caches for BPJ.
Operation has to be done tomorrow, Tuesday 23th of Feb, between 10am and 12pm CET
It concerns structure /BIC/CADTS_EXP000280000001
Tip : How to find structure name
1) run infopackage (view must contain records) and get it from the message
2) table RSDS
+ adding 0001 to the Application Structures
| DataSource | For WBD => BDJ | For WBQ => BQJ | For WBV => BVJ | For WBP => BPJ |
|---|---|---|---|---|
| DTS_EXP_FORE_DR_BW | /BIC/CADTS_EXP000360000001 | /BIC/CADTS_EXP000260000001 | /BIC/CADTS_EXP000170000001 | /BIC/CADTS_EXP000170000001 |
| DTS_EXP_FORE_BW | /BIC/CADTS_EXP000350000001 | /BIC/CADTS_EXP000250000001 | /BIC/CADTS_EXP000160000001 | /BIC/CADTS_EXP000160000001 |
| DTS_EXP_AERO_DR_BW | /BIC/CADTS_EXP000240000001 | /BIC/CADTS_EXP000200000001 | /BIC/CADTS_EXP000280000001 | /BIC/CADTS_EXP000280000001 |
| DTS_EXP_AERO_BW | ||||
| DTS_EXP_MTP_BW | /BIC/CADTS_EXP000470000001 | /BIC/CADTS_EXP000400000001 | /BIC/CADTS_EXP000380000001 | /BIC/CADTS_EXP000380000001 |
Field XXX is not a member of XXX even after a cache clearance on BPJ
A Java instance can have several servernodes for process execution (2 are available on BPJ).
Clearance might have been done on servernode 0, and loading is executed on servernode 1 which does still have previous structure definition
1- ask again cache clearance, in case clearance has not been done on both server node
2 - ask reboot of BPJ
For information, : Issue have been faced in nov 2020. Choice 1 has been done, but as BPJ has been reboot the day after, we can not say choice 1 is working
Column XXX not found
The field Name has to be up to 30c maximum
The field Name in DataSource has to be 16c maximum
Solution:
Ask DynaSys team to respect limits :
=> Table or View Name has to be up to 16c maximum
=> The field Name can be up to 30c but has to be unique on 16 first characters
=> new fields have to be added at the end of table otherwise transports to production have to be closely synchronized.
BW / DynaSys landscape (slides Etienne 19/01/2021)
