Orgchart portal integration

[Former Member]

Hello,

We are finalizing Orgchart deployment to QA environment.

I have trouble get the portal integration done. We are using SSO with logon ticket to connect to Orgchart.

When using URL iViews, it works fine but the main issue is that the whole URL is hard-coded in the iView property. This becomes an issue when transporting the iview to QA or PRD (iView pointing to Nakisa Dev server).

When using Nakisa iView template, we can configure a system alias, which we did. When opening the iView, a login page is displayed with the message "No user mapping defined for system Nakisa_System"

From my understanding, we don't need user mapping since we are using SSO.

Has anyone already configured the portal that way?

Thanks,

Laurent

[lukemarson]

Hi Laurent,

Did this work okay in DEV? Usually when we transport an iView into QAS we have to change the URL in the iView. This is slightly frustrating when transporting a larger number of Portal developments through environments, but I'm not sure what the solution is other than changing the URL manually.

I have not used a system alias before so I think just changing the URL in the iView is the easiest method.

I hope that helps!

Luke

[Former Member]

Since this morning, we got OrgChart successfully moved to QA. Here is what we did:

- From the Nakisa iView template, create a new custom iView template. Update the URL template with the right application. Protocol, Server and Port number remain dynamic. For example: <System.protocol>://<System.server>:<System.port>/OrgChart/default.jsp. Nakisa iView template is included is included with Nakisa portal package.

- In system administration, create a system using the Nakisa System template. Make sure an alias is defined for this system

- Create an iView based on your template. Define your alias as system name. If using SSO with logon ticket, remove the unnecessary user mapping parts

- A Nakisa system with the alias should be created in each environement (QA, PRD...)

With this, you can transport your iView across your system landscape without redefining iView URL.

[lukemarson]

Hi Laurent,

Well done on getting it all working and thanks for sharing this with the community. It's not something I know much about (I leave the Portal to someone else!) so this is useful to know.

Best regards,

Luke

[Former Member]

Hi Laurent,

I have come across the very same issue of hard coded URL's on the iview. I have seen your solution on using Nakisa template iviews and Nakisa template systems. As brilliant as the solution is, I suppose these templates are not delivered as part of standard Portal.

Can I ask you if you had your Nakisa and Portal deployed on the same cluster?

I our case, Nakisa is deployed on a separate CE system, which means no Nakisa packages on the Portal. Do you know what we would have to import into portal, in such a scenarion to enable us to use the Nakisa templates?

Thanks,
Ahsan

[Former Member]

Hi Laurent,

it could be a domain trust issue. Are you able to successfully log into OrgChart QA when hard-coding the URL to QA (without the alias)?

Please ensure you are using a fully-qualified domain name, example

MyQAHost.MyCompany.com/Orgchart

Thank you

Nabil