ASR NO field is not auto-populated on Manual ASRs

PROBLEM

ASR NO field is not auto-populated on Manual ASRs post ASR 53 upgrade.

CAUSE

Beginning with ASR 53 ,the code which used to auto-populate the ASR NO field for SENT orders has been removed.

If the CCNA and ICSC selected to generate the ASR order results in SENT order the ASR number will not be auto generated. However, if CCNA and ICSC are selected so as it generates RECEIVED order the ASR number will be auto populated on ASR order.

SOLUTION

To fix the problem, it is really required to understand the cause of the problem.

Let’s see what SENT and RECEIVED orders are.

For that look closely at CCNA and ICSC fields. So I created 2 CCNAs(1 as an owner and other as not) and 2 ICSCs(1 as an owner and other as not).

Create Access Customer

Login to M6 GUI and go to find links and search for Access Customer and click 'Add New'.

1. Create an Access Customer with "MetaSolv Solution Owner" checked.

2. Create an Access Customer with "MetaSolv Solution Owner" not checked.

Create ICSC

Login to M6 GUI and go to find links and search for ICSC and click 'Add New'.

1. Create an ICSC with "MetaSolv Solution Owner" checked.

2. Create an ICSC with "MetaSolv Solution Owner" not checked.

While creating CCNA and ICSC on the M6 GUI an indicator check ‘MetaSolv Solution Owner’ plays an important role.

Now lets create ASRs to see the ASR NO field is being populated or not.

Create SENT Order ASR

Go to Find Links and search for Service Requests and click 'Add New' and then select Access Service Request. 

ASR order should be created using CCNA which has ‘MetaSolv Solution Owner’ checked and ICSC which does not have ‘MetaSolv Solution Owner’ checked. 

The SENT order will not have ASR NO field auto-populated.

The RECEIVED order can also be verified from M6 database from SERV_REQ table in the SENT_RECV_CD column as below. Value 'R' is stored for RECEIVED orders.

Note: Please note ICSC value depends on CCNA value just have a close look what ICSC values you get while selecting CCNA. If CCNA is “owned” ICSC will automatically be “not owned” and vice versa.

Create RECEIVED order ASR

Go to Find Links and search for Service Requests and click 'Add New' and then select Access Service Request. 

ASR order should have CCNA of customer which is not the ‘MetaSolv Solution Owner’ so the CCNA should not have it checked.

The ICSC value will be picked accordingly. 

For RECEIVED orders the ASR NO field will be auto-populated.

The RECEIVED order can also be verified from M6 database from SERV_REQ table in the SENT_RECV_CD column as below. Value 'R' is stored for RECEIVED orders.

Hope this helps in understanding why ASR NO field is not populated on the ASR order.Please leave your feedback or query.

ASR installation for Metasolv 6.2.x

As mentioned in earlier posts our Metasolv installation is clustered so we will do ASR installation in clustered environment.

Pre Installation checklist

Metasolv 6.2.x is installed.

below paths are set as per your directory structure.

PATH= BEA_Home/jdk_version/bin $PATH
BEA_HOME=/opt/app/mss_home/bea(installation directory of Oracle Weblogic 10.3 server)
JAVA_HOME=/opt/app/mss_home/bea/jdk_version

Installation of ASR

STEP 1. 

From Metasolv installation directory mss_home run the following command.

java -jar Asr.releaseNo.buildNo_M62.jar

for version 53 it should be java -jar Asr.R53_0_0.b23_M62.jar

STEP 2.

The above java command will ask to choose Metasolv Home directory, a directory asr53installer(asr+version+installer) will be created in the selected directory.

It will automatically invoke setup.sh/setup.cmd in mss_home/asr53installer directory.

STEP 3.

Click Next.

STEP 4.

Enter the path and name of the MetaSolv Home directory, MetaSolv Domain directory, and MetaSolv Server directory or click Open to search for the directories.

STEP 5.

Click Next.

STEP 6.

Select any one of the following installation types:

•  Install all ASR Files
•  Install Only ASR EAR File

For a clustered environment, you can choose an option to extract the .EAR file only

For a non-clustered environment, choose the option to install and deploy all files.

STEP 7.

Click Next.

STEP 8.

Click Finish.

STEP 9. 

For a clustered environment.

1. Locate the loggingconfig_cluster-ASR53.xml file located in the mss_home/managedserver/appserver/config directory, where managedserver is the WebLogic managed server. 

Add the following snippet in appender element for ASR 53.

  <appender name="XMLFileAppASR53" class="org.apache.log4j.RollingFileAppender">
      <param name="ImmediateFlush" value="true"/>
      <param name="append" value="true"/>
      <param name="MaxFileSize" value="10000KB"/>
      <param name="MaxBackupIndex" value="10"/>
      <param name="File" value="${mslv.log.dir}/appserverlog_ASR53.xml"/>
      <layout class="com.metasolv.common.framework.logging.api.log4jext.xml.MSLVXMLLayout">
      </layout>
  </appender>

  <appender name="AuditFileAppASR53" class="org.apache.log4j.RollingFileAppender">
      <param name="ImmediateFlush" value="true"/>
      <param name="append" value="true"/>
      <param name="MaxFileSize" value="10000KB"/>
      <param name="MaxBackupIndex" value="10"/>
      <param name="File" value="${mslv.log.dir}/appserver_auditlog_ASR53.xml"/>
      <layout class="com.metasolv.common.framework.logging.api.log4jext.xml.MSLVXMLLayout">
      </layout>
  </appender>

Add the following snippet in category element for ASR 53.

  <category name="cmm.ASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
    <level value ="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
    <appender-ref ref="XMLFileAppASR53"/>
  </category>

  <category name="ASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
    <level value ="debug" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
    <appender-ref ref="XMLFileAppASR53"/>
  </category>

  <category name="cmm.SecurityASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
    <level value ="debug" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
    <appender-ref ref="AuditFileAppASR53"/>
  </category>

   
      2. Rename the file to loggingconfig_cluster-ASR53.xml.

STEP 10.

 RUN the ASR installation in each managed server instance.

STEP 11.

 Restart managed servers.

STEP 12.

RUN prodfixsql/procs sqls.

1. Run pfixSQL_Master.sql file located in the mss_Home/server/appserver/sql/ASR53/prodfixsql. This sql will call rest of sql files located in same directory.
2. Run the asr_master.sql file located in the mss_Home/server/appserver/sql/ASR53/procs directory that was created during the installation to apply the contents of the ASR procs directory to the database.

STEP 13.

1. Undeploy existing ASRversion.ear from application servers
2. Deploy ASRnewVersion.ear(cluster-ASR53.ear for clustered env) on application servers from admin console.

Changes done in STEP 9 will help in avoiding error while deployment.

“log4j: ERROR Attempted to append to closed appender named [XMLFileApp”

STEP 14.

Modify the gateway.ini , add below entry.

ASR53SERVER=MetaSolv.CORBA.WDIASR53.WDIROOT,MetaSolv.WDIASR53.WDIRootImpl

comment out similar entry for earlier version by placing a semi-colon in front of the entry.

;ASR52SERVER=MetaSolv.CORBA.WDIASR52.WDIROOT,MetaSolv.WDIASR52.WDIRootImpl

I hope this will help installing ASR newer upcoming versions, I will also try to post further the post ASR installation customization (e.g. generate java files from new IDL ASR files) for ASR new versions, please leave your feedback or query.

Metasolv Service Requests PSR, LSR, ASR, ISR explained

Service Requests in Metasolv

Before proceeding with Service Requests quickly understand LATA, LEC and IXC.

LATA(Local Access Transport Area)

A Local Access Transport Area (LATA) is a geographic area served by particular operating companies.
An IntraLATA call is a call made within a LATA.
An InterLATA call is a call made from one LATA to another

LECS AND IXCS

The local phone companies or Local Exchange Carriers (LECs) provide IntraLATA services.
The long distance phone companies or Interexchange Carriers (IXCs) provide InterLATA services.
Refer diagram above.

Now coming back to Service Requests.
Service Requests are the orders that a company receives for products or services. If a company needs a circuit, the company must use a service request to order it. If a company needs a piece of equipment, again it must submit a service request to order it.

Metasolv has following 4 types of service requests

1. Product Service Request (PSR)
2. Local Service Request (LSR)
3. Access Service Request (ASR)
4. Internal Service Request (ISR)

     Lets have a look at each one of them.

PRODUCT SERVICE REQUEST (PSR)

A product service request (PSR) supports requests for products from end users.
Some examples of products ordered include:

• Basic residential service
• Dedicated lines
• ISDN Basic Rate Interface (BRI)

End users place orders with their providers.

In the above example, 'Customer A' needs a private line to the 'Customer C'. Since both companies use the same local service provider, this scenario requires only one order.
CLEC receives the PSR for a dedicated line between 'Customer A' and 'Customer C'.

LOCAL SERVICE REQUEST(LSR)

A local service request (LSR) handles requests from local service providers for unbundled elements or resale services from the ILECs(Incumbent Local Exchange Carriers).
LSRs and Access Service Request (ASRs) are the two types of orders that are regulated. A regulated
order has to pass standards set by the Ordering and Billing Forum (OBF), which was created to
standardize orders so that all companies utilize the same elements when they submit a service request.

In this example, CLEC Telecom, a new local service provider, wants to provide local service to the XYZ area, which is currently being served by ABC-ILEC.
Before providing service to its end user customers, CLEC Telecom must purchase access to local loops and network interface devices.
The CLEC will attain all the unbundled elements. To accomplish this, it must send an LSR to the ILEC for the purchase of the unbundled elements in the XYZ area.

PURPOSE OF AN LSR

You can use a local service request to order any of the following:
• Local loop
• Network Interface Device (NID)
• Signaling and call-related database
• Local and tandem switch access
• Operator and directory assistance

ACCESS SERVICE REQUEST(ASR)

An access service request (ASR) is an order for terminating an access connection to a telephony network.

There are two main types of ASRs:
• Special Access ASR—For dedicated line telephone network entities (end user to ACTL or CO).
• Switched Access ASR—For trunks between network locations, ACTLs, Tandems, and COs.

SWITCHED ACCESS ASR

In the following example, a new LSP (CLEC Telecom) will begin serving customers in the area currently being served by ABC-ILEC.

Before providing local service, CLEC Telecom must complete the ASR for trunks connecting the switching equipment between the two LECs.

In the above example of a Switched Access ASR, an IXC called New IXC wants to sell long distance services to customers being served by CLEC Telecom.

First, New IXC must complete a switched access ASR for trunks between New IXC and CLEC Telecom.

SPECIAL ACCESS ASR

Parent/Child Relationship

A special access ASR is an order for dedicated line telephone network entities such as end user to
ACTLs or COs.

In this example, CustomerA orders a dedicated 56K line to the CustomerB in location B.
Since the two locations are not in the same LATA, the PSR for the private line generates two child
orders:

• One ASR to CLEC A for special access from CustomerA location to CLEC A ACTL(CO) in location A.
• Another ASR for special access to CLEC B from CustomerB's location to the CLEC B ACTL(CO).

INTERNAL SERVICE REQUEST

An internal service request (ISR) is simply that, an internal (within your own company) service
request. An ISR is the fastest and easiest order that you can place in the MetaSolv Solution.

Because ISRs are not validated against OBF guidelines, the MetaSolv Solution order-entry process for ISRs is very flexible. ISRs are often submitted as child orders to parent ASRs or PSRs.
Companies create ISRs to document inventory and to provision their own circuits. They use ISRs to
communicate to field personnel which equipment to assign to a circuit.
Also, some companies use ISRs as a standard to build all facility circuits.
Here are the types of circuits associated with an ISR:
• Facility circuits
• Trunks
• Special (for non-ordered circuits that are not facility circuits)
• Broadband (for ATM or frame relay, each of which require a facility circuit)

I hope I was able to explain the Metasolv Service Requests, please leave your feedback or query.