Configuration Fix for 1090 Error – SAP Spend Performance Management
A common configuration error is the 1090 Error, when the application is being launched or during the runtime. Error 1090 usually is an error about the related WebService maintenance, configuration or setup. Numerical Flex code indicates which area of the Flex application layer it belongs to. This WSDL invocation inconsistency is commonly caused by the following:
A. Issue: Incomplete configuration of the Portal template. It is usually caused by wrong WebAS port number,
Check: To validate whether or not this port number assigned correctly refer to the back-end’s transaction code SMICM, click on the icon called “Services” and look into your HTTP Service Port, then compare it to your Portal Template info you have indicated for WebAS port number field.
Fix: This port should match both places, if not adjust your information accordingly.
* Versions Affected: V2.0 and V2.1*
B. Issue: Incorrectly configured WebAS within the J2EE/ABAP configuration, using Java Port number and not BI-JAVA port, which should be used instead.
Check: For this exercise involve your BASIS expert (NOTE: Your usual HTTP port should be either 4 or 5 digit port number, respective to your NW’s system initial installation. Run BI Diagnostics Tool to see whether or not your port number is consistent.
Fix: The port number should be consistent with by appending the following URL to your existing URL [http://Versions Affected: V2.0 and V2.1
!https://weblogs.sdn.sap.com/weblogs/images/252114364/BIDiagnosticsToolB.jpg|height=315|alt=BI Diag Tool|width=700|src=https://weblogs.sdn.sap.com/weblogs/images/252114364/BIDiagnosticsToolB.jpg|border=0!
C. Issue: Inactive default NW Webservice Services is another reason why a user gets Error 1090. NW installation comes with a lot of default content of its own (depending on the version and installation method employed). In SICF we can see many services which an end-user may not be using at all, but many ask whether or not they need those services, and the answer is YES you do, as some of these services like WebDynPro or WebFlow, Workflow are required for operational process of your portal. For this, I recommend you to activate all of these webservices respectively (unless an end-user is absolutely certain/sure that some of those services are not required for their operational process).
Check: Login to your system in the back-end and type your SICF transaction code, then press on green check for an acknowledgment. Browse through your default_host until you reach /sap/bc area, then select “bc” as domain and right-click to activate the content under this domain.
Fix:Activate everything under the tree not just tree alone. Ensure you’re able to run your WebDynPro related services like Content Administrator / WebDynPro JCOs and SLD Setup tools).
NOTE: Also ensure you have activated SAP Spend Performance Management related services under /sap/bc/srt/rfc/sap > RS_BCT (all of them) and RS_BXT (only 1 service).
Versions Affected: V2.0 and V2.1
* <strong>!https://weblogs.sdn.sap.com/weblogs/images/252114364/SICFServiceActivationC.jpg|height=412|alt=SICF services|width=700|src=https://weblogs.sdn.sap.com/weblogs/images/252114364/SICFServiceActivationC.jpg|border=0!</strong> </div><div class=”msocomtxt”>!https://weblogs.sdn.sap.com/weblogs/images/252114364/ContentAdminWebDynProCheckC.jpg|height=318|alt=WebDynPro check|width=700|src=https://weblogs.sdn.sap.com/weblogs/images/252114364/ContentAdminWebDynProCheckC.jpg|border=0!*
D. Issue: SOAMANAGER Transaction Code doesn’t have “Access J2EE Information” provided. This task would require your BASIS level configuration changes to correctly setup the WebAS redirection policy.
Check: Request SOAMANAGER t-code in your back-end system, then click on Global Settings hyperlink displayed in the Technical Configuration Tab. Global Settings will bring you its menu where you can find Access J2EE Information tab.
Fix: Click on the tab and input your HTTP Port number and your domain name accordingly.
Versions Affected: V2.0 and V2.1
E. Issue: Undefined WSADMIN for the application Webservices. WSADMIN, even though in the process of being obsolete, is still valid and for the webservice distribution processes.
Check: If any RS_BCT, RS_BXT or OPM_DM* webservices (OPM_DM_X_API being the most critical) in WSADMIN under SOAP Application for RFC-Compliant FMs are not visible, need to create these from WSCONFIG (see side-effect F for details). If these services are available, WSADMIN t-code and clicking WebService Homepage.
*Fix: Prior to this test a user has to maintain main domain URL within GoTO -> Administration Settings as follows http(s)://<hostname>:<port number> – derived from the J2EE standalone port (your Portal Port Number and NOT BI-Java / SMICM port number). Your test has to be performed in RPC Style and including SAP Features in WSDL. Your result should be a successful redirection to the page with your selected WebService. If you were able to get this process done, then your WSADMIN definitions are set accordingly.</p><div class=”msocomtxt”>Versions Affected: V2.0 and V2.1*
!https://weblogs.sdn.sap.com/weblogs/images/252114364/WSAdminandAdministrationSettingsPortE.jpg|height=247|alt=WSAdmin Port Check|width=700|src=https://weblogs.sdn.sap.com/weblogs/images/252114364/WSAdminandAdministrationSettingsPortE.jpg|border=0!
!https://weblogs.sdn.sap.com/weblogs/images/252114364/WSAdminandlistofwebservices1E.jpg|height=422|alt=WSAdmin WS List|width=700|src=https://weblogs.sdn.sap.com/weblogs/images/252114364/WSAdminandlistofwebservices1E.jpg|border=0!
!https://weblogs.sdn.sap.com/weblogs/images/252114364/WSAdminandlistofwebservices2E.jpg|height=391|alt=WSAdmin WS List 2|width=700|src=https://weblogs.sdn.sap.com/weblogs/images/252114364/WSAdminandlistofwebservices2E.jpg|border=0!
F. Issue: Webservices for the application not installed…
Fix: To correct this, access WSCONFIG and add the services (create new), in the following fashion: Select your desired webservice (e.g. OPM_DM_X_API, by clicking on the Web Service field and on F5/Browse) and assign it the same variable name, then click on Create New and on SAVE respectively. Check your service for consistency by clicking on the “consistency check” icon, to ensure that it’s created accordingly and not as empty string. If a user is asked to create a local transport job, indicate the reason behind your local transport job, save it and assign every other WSCONFIG webservice you’re trying to create for Spend Performance Management (under RS_BCT and RS_BXT, besides OPM_DM_X_API) to this transport job. Once you have created those individual services 1 by 1, check whether or not they do correspond in WSADMIN respectively. Note: It’s easy enough to miss 1 webservice to be delivered from WSCONFIG to WSADMIN therefore pay close attention to your manual journey. (NOTE: In earlier versions of NW SPS 13 and below, very rarely a user will not even able to locate webservices in WSCONFIG, for further steps on this process please see installation and configuration guide / Redelivering Webservices from SCC1/SCC4).
*Versions Affected: V2.0 *
G. Issue: Inconsistent / corrupted version of your BIBASE-S and BIWEBAPP components (your default NW components). Quite often users install different versions of components of their NW J2EE layer (portal, visual admin, configtool). This may cause an inconsistency established between J2EE level dependencies (like BIBASE-S and BIWEBAPP), please take a note of it. Always keep those two components on the same SP and Patch level (most recent upgrades available in SAP’s SMP).
*Check: Login to your index.html page and click on System Information. Ensure you login to Sys Info again with your admin user credentials. Click on “All Components” Hyperlink and find your BIBASE-S and BIWEBAPP components (ensure they are exactly off the same build e.g. meaning same release, sp and patch levels).</p><p style=”margin: 0in 0in 0pt 0.5in” class=”MsoListParagraph”>Fix: If the components are different, DO NOT downgrade, instead upgrade to the same SP level.</p><p style=”margin: 0in 0in 0pt 0.5in” class=”MsoListParagraph”>Versions Affected: V2.0 and V2.1</p><p style=”margin: 0in 0in 0pt 0.5in” class=”MsoListParagraph”> </p><div class=”msocomtxt”>!https://weblogs.sdn.sap.com/weblogs/images/252114364/SystemInfoBIBASEandBIWEBAPPG.jpg|height=445|alt=BIBase|width=700|src=https://weblogs.sdn.sap.com/weblogs/images/252114364/SystemInfoBIBASEandBIWEBAPPG.jpg|border=0! *