Author Topic: Create programming documentation, export programming data to XML  (Read 7647 times)

Offline petr.necas

  • Sr. Member
  • ****
  • Posts: 393
  • Country: cz
  • Karma: +8/-0
    • View Profile
Hi all, I'm almost done with the programming of ICP for our new customer. They requested a document that will summarize all the programming done in the System Administration Tool. The only way I can think about is to use export feature in each of the form where I did any programming and formatting the exported files into some nice word document. This could however be very tedious job.

What I would like to have is ability to export all the configuration, e.g. in XML file that I would send to the customer.

or, maybe to have some tool that would convert the backup file to some readable text form (e.g. XML) or connect to the ICP and read the programming data and do some nice export.

Having this would help me much, e.g. when I need to compare what changes have been done in the programming (simply I could compare two TXT/XML files and) or just quickly review the programming without having to visit each form (over slow remote connection is real nightmare).

I know, somebody can suggest there is an Audit Trail Log but this would not be a solution in this case.

Do you have any ideas?

Petr


Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #1 on: June 27, 2013, 04:08:48 PM »
How about printing it from the SX2000 interface.
It doesn't print everything but will almost everything.
Connect via putty to port 23.  Be sure to enable logging.
from maintenance enter "form all /po lpr3"
Then enter "en pr/n"
It could take a couple of hours but it will print out almost all the forms.

Ralph


Offline petr.necas

  • Sr. Member
  • ****
  • Posts: 393
  • Country: cz
  • Karma: +8/-0
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #2 on: June 27, 2013, 04:37:00 PM »
Hi Raplh, I tried to log in but always got login incorrect message. I tried with the system account, even created a new account with system admin policy "root" and "system", in putty I tried connection type Telnet and Raw, both on port 23. Any ideas?

Petr

Offline Mitel100

  • Sr. Member
  • ****
  • Posts: 262
  • Country: gb
  • Karma: +6/-0
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #3 on: June 27, 2013, 05:16:17 PM »
Using telnet to login into the DB, will us the default SX2000 passwords.

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #4 on: June 27, 2013, 05:43:42 PM »
Sent you a PM with the passwords.

Ralph

Offline petr.necas

  • Sr. Member
  • ****
  • Posts: 393
  • Country: cz
  • Karma: +8/-0
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #5 on: June 27, 2013, 06:40:33 PM »
Trying my best but the syntax "form all /po lpr3" is not accepted, what is accepted is e.g. FORM ARS /ALL /PO LPR3.
Petr

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #6 on: June 28, 2013, 09:32:43 AM »
Sorry.  Doing this from memory.
try "form /all /po lpr3"


Ralph

Offline petr.necas

  • Sr. Member
  • ****
  • Posts: 393
  • Country: cz
  • Karma: +8/-0
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #7 on: June 28, 2013, 03:47:48 PM »
Hi Ralph, I'm getting this:

Command not supported by system - Command IGNORED
form /all /po lpr3

I don't know what could be wrong.
Petr
« Last Edit: June 28, 2013, 04:08:38 PM by petr.necas »

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #8 on: July 01, 2013, 09:45:49 AM »
What version of software are you running?

I haven't tried this is a very long time so it may not work any longer.

Ralph

Offline petr.necas

  • Sr. Member
  • ****
  • Posts: 393
  • Country: cz
  • Karma: +8/-0
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #9 on: July 01, 2013, 09:48:46 AM »
Hi Ralph, I'm using MCD 5.0 SP2 PR2.

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #10 on: July 01, 2013, 09:56:53 AM »
Just tested on my system.  Sorry.   The /all option isn't supported any longer for printing the entire system.
That's a shame.  When I needed it, it worked quite well for me.

You can still do one form at a time.   
Try this for hunt groups:  fo hu /all /po lpr3

Ralph

Offline petr.necas

  • Sr. Member
  • ****
  • Posts: 393
  • Country: cz
  • Karma: +8/-0
    • View Profile
Re: Create programming documentation, export programming data to XML
« Reply #11 on: July 01, 2013, 10:26:37 AM »
Hi Ralph, thank you for reply, I was playing with this during the weekend and found out that even from the Maintenance Commands I was able to run the FORMPRINT command. When I connected to to the port 1754 I could read the formprint command output that was sent to LPR1. For example I was able to run following commands:

FORMPRINT DIM A F D /PORT LPR1
FORMPRINT PATH ASS /INSTANCE 0 /PORT LPR1
FORMPRINT TEL DIR /PORT LPR1
FORMPRINT SY SP /PORT LPR1
FORMPRINT U /PORT LPR1
FORMPRINT RO A /PORT LPR1

The only challenge I had was to find the correct name of the form (requires old frame names) and that some forms did not support /ALL parameter but /INSTANCE <number>. In the system help there is a page that shows what are the old and corresponding new frames names, but for some forms it did not work anyway.

In order to create some documentation, I will probably run Export on all the frames manually and then try to extract the data either manually or create some script that will convert the CSV data to some usable form.
Petr


 

Sitemap 1 2 3 4 5 6 7 8 9 10