# ENtire X requirements

**URL:** <https://techcommunity.softwareag.com/t/entire-x-requirements/244229>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-on-Linux, EntireX\
**Created:** [September 13, 2021, 7:42am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229 "2021-09-13T07:42:46Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon55491631](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@anon55491631](https://techcommunity.softwareag.com/u/anon55491631)\
**Post date:** [September 13, 2021, 7:42am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/1 "2021-09-13T07:42:46Z")

</div>

#### What product/components do you use and which version/fix level?

Natural adabas ENtire X on Linux  
ADabas NAtural on Windows

#### What are trying to achieve? Please descibe in detail.

Customer is doing RPC call with Entire X to the linux server to access adabas data on the Linux server the ENtire X with a broker running on LInux. this works. they would now like to do it the other way round and do call to Windows for data from the Adabas / Natural application running remotely. they only have ADabas and Natural installed on all the windows server. i have shown the we can do this with ADATCP/ Entire Net-work but they want to look at an Entire X solution as well. would they need a full Entire X or just a runtime on the windows servers..

#### Do you get any error messages? Please provide a **full error** message screenshot and log file.

---

<div class="post-metadata">

**Author:** ![Finn\_the\_Dane1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/finn_the_dane1/32/132_2.png) [@Finn\_the\_Dane1](https://techcommunity.softwareag.com/u/Finn_the_Dane1)\
**Post date:** [September 13, 2021, 8:22am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/2 "2021-09-13T08:22:39Z")

</div>

The short answer is: You’ll need to contact your Software AG Account manager!  
EXX has been sold in various setups over the years.

But from a technical point of view it is piece of cake.  
When you have the IDL file in Designer (EXX or ONE perspective) you simply select Natural/Generate RPC-client and you have a working Subprog and also test-program.  
Finn

---

<div class="post-metadata">

**Author:** ![anon55491631](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@anon55491631](https://techcommunity.softwareag.com/u/anon55491631)\
**Post date:** [September 13, 2021, 2:48pm UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/3 "2021-09-13T14:48:03Z")

</div>

yes that works currently on the windows box they don’t have Entire X or a broker to call.

---

<div class="post-metadata">

**Author:** ![Finn\_the\_Dane1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/finn_the_dane1/32/132_2.png) [@Finn\_the\_Dane1](https://techcommunity.softwareag.com/u/Finn_the_Dane1)\
**Post date:** [September 14, 2021, 8:11am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/4 "2021-09-14T08:11:11Z")

</div>

Any reason why you couldn’t use the broker on Linux ?

Regarding the right to use the windows exx client - again check with contract/account manager 😉  
Finn

---

<div class="post-metadata">

**Author:** ![anon55491631](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@anon55491631](https://techcommunity.softwareag.com/u/anon55491631)\
**Post date:** [September 14, 2021, 9:04am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/5 "2021-09-14T09:04:37Z")

</div>

Hi Finn

This is what I am trying to establish before I talk to the account manager on what software the customer needs. How would a call be made from the Linux Natural application to the natural application on Windows if there is no Entire X installed on the windows.

Ian

---

<div class="post-metadata">

**Author:** ![Finn\_the\_Dane1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/finn_the_dane1/32/132_2.png) [@Finn\_the\_Dane1](https://techcommunity.softwareag.com/u/Finn_the_Dane1)\
**Post date:** [September 14, 2021, 9:57am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/6 "2021-09-14T09:57:52Z")

</div>

So you will need to start a Natural RPC-server on Windows, which could connect to the Broker on Linux.  
For starting a Natural RPC-server you will need a parameterfile where you specify that it should start as an RPC-server under a specific name and to which broker it should connect.  
When you have created the parmfile then start it …

* * *

**To start a Natural RPC server under Windows**

1. Create a shortcut for Natural.
2. Enter the shortcut properties.
3. In the **Target** text box, edit the Natural path and append:  
“\natural.exe” batchmode parm=serverparm  
where `serverparm` is the name of the parameter file.

* * *

I haven’t checked if the newer versions of natural requires a licensefile for the EXX-client Stub like the java stub does, but up until recently it was part of the standard installation.

Hope that was enough for your “pre-contact” investigation 😉  
Finn

---

<div class="post-metadata">

**Author:** ![anon55491631](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@anon55491631](https://techcommunity.softwareag.com/u/anon55491631)\
**Post date:** [September 14, 2021, 11:23am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/7 "2021-09-14T11:23:47Z")

</div>

Thank you will give it a bash

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [December 13, 2021, 11:24am UTC](https://techcommunity.softwareag.com/t/entire-x-requirements/244229/8 "2021-12-13T11:24:35Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
