By all means, Tark4 is a part of GN4, so when you install GN4 you have also all Tark4 functionalities. In some circumstances you may want to have two different browser interfaces for GN4 and Tark4: the GN4 one to serve contributors and reporters on-the-road, and the Tark4 one to serve librarians and/or external Tark4 users.

How it works?

The Editorial_Installconfig loads the GN4 schema and its configuration and data files. Gn4 schema and configuration include all Tark4 objects and configuration, so you don’t need to do anything with Tark4_installconfig, that is needed only for Tark4 "only" installations, not including gn4 objects such as article and page.

So, GN4 indeed includes Tark4.

The web interface configuration, at this moment, is only one and it’s a mix of search and display of gn4 and archive objects.

The main web application is composed of pages, that are files in the configuration files named gnpc_webparts_[name of the page].xml.

You can see the list of those, as loaded by the gn4_installconfig:

<!-- user interface tabbed pages-->

<ConfigFile Scope="WebParts">Global\gnpc_WebParts_budgets.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpc_WebParts_events.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpc_WebParts_folder.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpc_WebParts_tasks.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpc_WebParts_trashcan.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4\gnpc_WebParts_editions.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4\gnpc_WebParts_home.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4\gnpc_WebParts_search.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4_Tark4_Common\gnpc_WebParts_contacts.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4_Tark4_Common\gnpc_WebParts_publish.xml</ConfigFile>

 

So, opening either http://myserver/gn4 or http://myserver/tark4 will show those pages.

To distinguish them, you have two choices.

Sub virtual directory

You can create a subfolder of the GN4 application, and associate different configuration pages to that.

For example, creating a virtual dir under gn4:

http://myserver/gn4/archive

you could then rename a page config to match the application name:

gnpcArchive_WebParts_search.xml

and load it using:

cmd4 config -in gnpcArchive_WebParts_search.xml -username xxxx -password -yyyy

where xxxx is the name of a GN4 user who can logon to system with sufficient permissions to perform this operation and yyyy is the password.

Note: the above connects to the default connection: should you want to specify the connection or server name, see cmd4 examples.

Now access the http://myserver/gn4/archive, and you will see the search page tab only.

So the rule is that the tabs are loaded based on the application name.

And the root application has no name, so gnpc_webparts_xxx.xml are loaded by it.

The INT application loads the gnpcInt_webparts_xxx.xml.

A Jack application will load the tabs imported as gnpcJack_webparts_xxx.xml.

Two independent urls

You may want to have two independenturls:

http://myserver/gn4

and

http://myserver/tark4

or maybe install the apps on the root of iis:

http://gn4

http://tark4

In this case, you need to duplicate the web/gnportal folders, and for one of the two applications, modify the web.config, the setting:

<add key="Web.RootsToAppendToAppName" value="" />

That is commented by default, allow the definition of a custom “name” to load the proper config.

In the above example, to have your custom pages loaded when accessing the url:

http://myserver/tark4

you will need to set the key to:

<add key="Web.RootsToAppendToAppName" value="/Tark4;" />

And import pages config named:

gnpcTark4_webparts_xxx.xml

All the pages, whatever the name of the application, will load and use the configurations (directory styles, searches, editobject uis…) defined in the files:

Baseportalconfig.xml

Portalconfig.xml

The root application will also load and use the:

Gnpc_config.xml

The Int application will also load and use gnpcInt_config.xml.

And the Tark4 application should load also the gnpcTark4_config.xml.

So if you want to share configsurations, define them in portalconfig.xml.

(courtesy of Marco Rebasti)