Fixes are available
Closed as program error.
When we navigate AS2 profiles wizard (use existing identity) then change the identity name and click next and again click back. Now from this screen it throws an error. Not able to create AS2 Profiles for same Identity in different Roles
Workaround 1: Use the Existing Identity option and modify the AS2 Identifier - This works in full SI as well as for AS2 Edition. 1.Create a new Organization as in Step 1 of Simulation Steps. You can verify from Trading Partner > Setup >Advanced that the following are created for the Organization: Identities Transport Packaging Document Exchange Delivery Channel Profile 2.Create a new Partner from AS2 UI using option "Use an existing Identity." On the page that follows, change the AS2 Identifier (for example: If the existing value of AS2 Identifier is 12345 change it to 123456), then continue to populate other fields as required and save the Partner profile. You can verify from Trading Partner > Setup >Advanced that the following are created for the Partner: Transport Packaging Document Exchange Delivery Channel Profile NOTE: Another entry for Identity is not created since an existing identity was used. The identifier value in the existing identity is modified to 123456. 3. From AS2 UI, go back to the Partner created in step 2 and change the identifier back to the original identifier of the Organization (for example, change the identifier from 123456 to 12345) and save the changes. 4. Go to Trading Partner > Setup > Advanced and verify the following: There are 2 entries each for the following - One for the Organization created in step 1 and one for the partner created in step 2 and modified in step 3. Transport Packaging Document Exchange Delivery Channel Profile However, there is still only 1 entry for Identity and the identifier in this identity is now modified back to 12345 . NOTE : There are no duplicate / redundant entries for transports etc ., created when Step 3 is executed. There is only 1 set created when the partner is created in step2. Once the identifier is changed back to original AS2 identifier , there are no new entries created .( This is because, these are linked to the identity name and not the identifier. So any change in identifier does not create any new transport , document exchange etc) The above workaround can be used to create a new trading partner or organization from an existing organization (or partner). Workaround 2 - Directly create the trading partner from Trading Partner > Setup > Advanced (this will not work for AS2 Edition users since they do not have access to Trading Partner > Advanced Menu as well as BP creation). Follow the steps below: 1.Go to Trading Partner > AS2 UI > Create New AS2 Partner or Organization > Create an Organization. You can verify from Trading Partner > Setup > Advanced that the following are created for the Organization: Identities Transport Packaging Document Exchange Delivery Channel Profile 2.Go to Trading Partner > Setup > Advanced and create a new Transport, Packaging, Document Exchange, Delivery Channel, Profile. While creating each of these you will have to select the identity created in Step 1 of this workaround. This way, a new set of Transports etc are created using an existing identity. Once Step 2 is executed, there are two ways to proceed: Method 1: Add an entry in the AS2_PROFILE table so that the newly created organization or partner profile will be accessible from the AS2 UI and can directly be used to create relationships between organization and partner. Profiles created from Trading Partner > Advanced are not visible from AS2 UI unless the relevant information is added to table AS2_PROFILE. We require these to be accessible from AS2 UI so that out of the box support like Mailbox / File System Storage and BPs will be available. The procedure is as follows: To add a Partner profile to AS2 UI use the query below: INSERT INTO AS2_PROFILE VALUES ('-5cc16c05:13a6ea71321:2694','N','N','HTTPClientAdapter',1,CURR ENT TIMESTAMP,CURRENT TIMESTAMP,'InstallProcess','InstallProcess','UI','UI') The values to be supplied are : PROFILE_ID,IS_ORG,IS_ORIGINAL_ORG,HTTP_CLIENT_ADAPTER,LOCKID,CRE ATETS,MODIFYTS,CREATEUSERID,MODIFYUSERID,CREATEPROGID,MODIFYPROG ID Out of the values to be supplied above, you will have to modify only the following : PROFILE_ID - This can be obtained from Trading Partner > Advanced > Profiles ( Once step 2 is executed). HTTP_CLIENT_ADAPTER - Name of HTTP Client Adapter Instance CREATETS- Time of creation of Partner Entity ( Each DB type has a different function/method for obtaining this information ) MODIFYTS-Time of modification of Partner Entity (Each DB type has a different method for obtaining this information) To create an Organization from a partner or an existing organization, use the following query: INSERT INTO AS2_PROFILE VALUES('-1e8cf097:13a74c3ab41:-2ed2','Y','N','',1,GETDATE(),GETD ATE(),'InstallProcess','InstallProcess','UI','UI') The values to be supplied are: PROFILE_ID,IS_ORG,IS_ORIGINAL_ORG,HTTP_CLIENT_ADAPTER,LOCKID,CRE ATETS,MODIFYTS,CREATEUSERID,MODIFYUSERID,CREATEPROGID,MODIFYPROG ID Out of the values to be supplied above, you will have to modify the following: PROFILE_ID - This can be obtained from Trading Partner > Advanced > Profiles (Once step 2 is executed) HTTP_CLIENT_ADAPTER - This value is null for an organization profile CREATETS - Time of creation of Partner Entity (each DB type has a different function/method for obtaining this information) MODIFYTS - Time of modification of Partner Entity (each DB type has a different method for obtaining this information) In addition to this, email information of an organization profile can be updated through table AS2_EMAIL_INFO using query: INSERT INTO AS2_EMAIL_INFO values ( ENTITY_ID, PROFILE_ID,EMAIL_ADDRESS,EMAIL_SERVER,EMAIL_PORT) ENTITY ID is obtained from table YFS_ORGANIZATION using query : select * from YFS_ORGANIZATION where ORGANIZATION_KEY ='ABC' and ABC is Identity name of existing identity. Method 2: Once Step 2 is executed, you will then have to create a contract between the required profiles (organization and partner), then do the required end to end setup. AS2 UI cannot be used at any stage since all entities created from Trading Partner > Advanced will not be visible in AS2 UI.
Users Affected: All users of AS2 multi-org Problem Description: 1. Not able to create AS2 Profiles for same Identity in different Roles 2. AS2 throws error when clicking next and back and again next when we change the identity name Platforms Affected: All
Resolution Summary: Added multi-org check which will allow creating the profile using the same identifier. Delivered in: 5104, 5020401_1, 5103_1
Published on 12/28/12
Reported component name
STR B2B INTEGRA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR B2B INTEGRA
Fixed component ID
Applicable component levels
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.