Hi,
at the moment I'm trying to make the SolMan - ARIS Synchronisation work.And after installing everything like I was told in the administration-handbook,I get the error in ARIS Business Architect for SAP 7.1: "sapjco.jar not found"
I'm using the SAP JCo 3.0.5. which is the latest I think.Does ARIS BA for SAP 7.1 work with a 3.x JCo?
LocalServer is used.
Any suggestions?
Michi
Hi Michael,
ARIS 7.1 does not support the JCO 3.x versions, you have to use the 2.1.x versions of the SAP JCO. Sorry.
BR,
Sascha
Here are other community entries for the SAP JCO topic:
http://www.ariscommunity.com/users/rahulrajvanshi31/2009-12-10-errors-solman-aris-synchronization
http://www.ariscommunity.com/users/ajeshkumarts/2010-01-25-issues-aris-business-designer-sol-man-sync
mhm,actually I'm not that experienced with the handling of transactions, but it seems odd that synchronisation is running but transactions don't.
Did you disable the use default server checkbox at View/Options/SAP Options/Select Server ?Did you also select a Default Server? (in ARIS)
Make sure you enabled the Use transactions with SAP Solution Manager - Check Box at View/Options/SAP options/Solution Manager. (in ARIS)
Did you transfer the current transport request to the SAP System. There is one transport request for synchronisation and another one for Customizing Transactions.
That's all I got.
Best Regards
Michi
can you explain which transport requests need to be done ?
We manage to do the synchronisation both way. but now we want "not using" the synchronisation to be able to display transaction from ARIS publisher i thought if we have the attribut "transaction code" fill for the sap object it should be possible!.
can you advice?
thanks
Genevieve
Hi,
there are two different approches to start a transaction:
1. Run default SAP transactions (e.g. VA01) from any SAP system: This approch works without
a transport request on the Solution Manager system. You have to maintain the transaction
code (e.g. VA01) in the attribute "Transaction code" which is available for the objects
(screen objects, functions, ...) or model types like the EPC.
2. Run Solution Manager transactions: This approch needs a sychnchronized Solution Manager project wich contains Solution Manager transactions (screen objects). The transport request which is needed for the Solutin Manager synchronisation is also necessary for the start of such Solution Manager transactions over the Solutin Manager.
Solution manager transactions can be of type "SAP Transaction" then it is possible to start such a transaction over the selected server (any SAP system) which don't need the transport request.
Best Regards
Sascha